GENBRK(1)

💖 GENBRK — bestie edition 💖

okay so this is genbrk(1), straight outta the ICU 78.3 Manual, and it's literally the little tool that turns your break iteration rules into binary data files. sit down, grab a boba, we're doing this 🧋✨

---

✨ NAME ✨

genbrk — compiles ICU break iteration rules source files into binary data files. that's it, that's the job, and she does it flawlessly 💅

---

🌸 SYNOPSIS 🌸

genbrk [ -h, -?, --help ] [ -V, --version ] [ -c, --copyright ] [ -v,
--verbose ] [ -d, --destdir destination ] [ -i, --icudatadir directory ]
-r, --rules rule-file -o, --out output-file

---

🦋 DESCRIPTION 🦋

so genbrk reads the break (boundary) rule source code from rule-file and creates a break iteration data file. no cap. and normally? that data file has the .brk extension. that's her signature move 🎀

the details of the rule syntax can be found in ICU's User Guide. iykyk 📖

---

💅 OPTIONS 💅

• -h, -?, --help — print help about usage and exit. the "hey bestie what do i do" button 🫶
• -V, --version — print the version of genbrk and exit. main character introduction ✨
• -c, --copyright — embeds the standard ICU copyright into the output-file. legal slay 👑
• -v, --verbose — display extra informative messages during execution. she's yapping and honestly? we're listening 💬
• -d, --destdir destination — set the destination directory of the output-file to destination. where she drops the goods 📁
• -i, --icudatadir directory — look for any necessary ICU data files in directory. for example, the file pnames.icu must be located when ICU's data is not built as a shared library. the default ICU data directory is specified by the environment variable ICU_DATA. most configurations of ICU do not require this argument. so like, usually you can skip it 🧚
• -r, --rules rule-file — the source file to read. the input, the origin story 🌱
• -o, --out output-file — the output data file to write. the glow-up destination 🌈

---

😭 CAVEATS 😭

okay listen, this part is important, don't scroll past it.

when the rule-file contains a byte order mark (BOM) at the beginning of the file, which is the Unicode character U+FEFF, then the rule-file is interpreted as Unicode. without the BOM, the file is interpreted in the current operating system default codepage.

so basically: no BOM = your OS's default codepage decides your fate. chaotic behaviour, not the cute kind 💀

in order to eliminate any ambiguity of the encoding for how the rule-file was written, it is recommended that you write this file in UTF-8 with the BOM. fr fr, just do it 🙏

---

🌈 ENVIRONMENT 🌈

• ICU_DATA — specifies the directory containing ICU data. defaults to ${prefix}/share/icu/78.3/. some tools in ICU depend on the presence of the trailing slash. it is thus important to make sure that it is present if ICU_DATA is set.

not the trailing slash being load-bearing 😭 do NOT forget it, bestie, the tools will simply not vibe

---

🫶 AUTHORS 🫶

• George Rhoten
• Andy Heninger

the icons who made her 👑

---

⭐ VERSION ⭐

1.0

---

💜 COPYRIGHT 💜

Copyright (C) 2005 International Business Machines Corporation and others

---

🔥 SEE ALSO 🔥

http://www.icu-project.org/userguide/boundaryAnalysis.html

---

and that's the whole page, bestie 🎀 this was ICU MANPAGE, dated 2 December 2005, and she's still serving GENBRK(1) energy to this very day. go compile something gorgeous 💖✨