UNICODE_GRAPHEME_BRE(3)

📦
version 2.6.0 · 7 versions
, in nixpkgs unstable, ubuntu stonking

💖 UNICODE_GRAPHEME_BRE(3) 💖

okay bestie, so this is a page from the Courier Unicode Library and it's literally all about unicode grapheme cluster boundary rules — aka "where do I actually cut this text so I don't slice a letter in half" energy. no cap, this is the good stuff. ✨

🌸 NAME 🌸

unicode_grapheme_break, unicode_grapheme_break_init, unicode_grapheme_break_next, unicode_grapheme_break_deinit — the unicode grapheme cluster boundary rules, periodt.

🎀 SYNOPSIS 🎀

#include <courier-unicode.h>

unicode_grapheme_break_info_t unicode_grapheme_break_init(void);

int unicode_grapheme_next(unicode_grapheme_break_info_t handle,
                          char32_t c);

void unicode_grapheme_deinit(unicode_grapheme_break_info_t handle);

int unicode_grapheme_break(char32_t a, char32_t b);

🦋 DESCRIPTION 🦋

These functions implement the unicode grapheme cluster breaking algorithm. it's giving ✨text segmentation✨ and we're obsessed.

Call unicode_grapheme_break_init() to initialize the grapheme cluster breaking algorithm. unicode_grapheme_break_init() hands you back an opaque handle — like a little backstage pass 🎟️, you don't peek inside it, you just hold it and pass it around.

Then every time you call unicode_grapheme_break_next(), you give it that handle plus the next character. unicode_grapheme_break_next() returns a non-0 value if there's a grapheme break before the character, inside a sequence of Unicode characters. so non-0 means "cut here bestie ✂️", zero means "nah, this char is glued to the last one".

unicode_grapheme_break_deinit() releases all the resources used by the grapheme breaking handle, and the unicode_grapheme_break_info_t handle is no longer valid after this call. like, it's done, it's retired, do NOT text it back 💀 one and done.

🫶 tiny lil heads-up that lowkey matters: the first call to unicode_grapheme_break_next() always returns non-0, as per the GB1 rule. yes always. that's just the rule, iykyk.

unicode_grapheme_break() is the simplified little interface — it returns non-zero if there is a grapheme break between two unicode characters a and b. it's the lazy-girl route and honestly? iconic.

It is equivalent to calling unicode_grapheme_break_init(), followed by two calls to unicode_grapheme_break_next(), and finally unicode_grapheme_break_deinit(), then returning the result of the second call to unicode_grapheme_break_next(). so if you ever wondered "what is this function doing under the hood", that's the whole tea ☕✨

👑 SEE ALSO 👑

🫶 AUTHOR 🫶

Sam Varshavchik Author

💅 NOTES 💅

  1. TR-29 https://www.unicode.org/reports/tr29/tr29-47.html

and that's the whole page bestie, you ate it 💖 this was the Courier Unicode Library doc, version dated 04/12/2026, and we are officially caught up on our grapheme cluster breaking rules. main character Unicode knowledge, fr fr. go break some clusters responsibly 🌈🎀💜

📦 where this page comes from