CLDRPARSER-3.2.2(1)

📦
version 3.2.2 · 5 versions
, in ubuntu stonking

💖 CLDRPARSER-3.2.2(1) 💖

okay bestie, welcome to the manual page for cldrparser-3.2.2, part of the Free Pascal Compiler (FPC) manual, section 1. and listen. this page is unhinged in the most iconic way, because it just dumps the program's own argv-parse errors at you, over and over, like a group chat where someone keeps re-sending the same screenshot. 🫶 we're gonna read every single one. no skipping. periodt.

✨ NAME ✨

cldrparser-3.2.2 — CLDR to pascal translator for Free Pascal Compiler (FPC) 💅

🌸 DESCRIPTION 🌸

so the very first thing the DESCRIPTION hits you with is literally the binary complaining about its own command line:

/build/fpc-gpPkVv/fpc-3.2.2+dfsg/debian/tmp/usr/bin/cldrparser-3.2.2: illegal option -- -

and then, right after that, the actual useful sentence:

This program creates pascal units from CLDR's collation files for usage with the FreePascal Native Unicode Manager.

icons only. 🌈 then it shows you how to actually call it:

Usage : cldrparser <collationFileName> [<typeName>] [-a<alt>] [-d<dataDir>] [-o<outputDir>] [-t<HaltOnFail>]

where :

  • collationFileName — the target file, bestie. specify it. 👑
  • typeName — optional! this is the collation's type-name to be parse.

and if you don't hand over that typeName argument, it picks a default type-name for you, walking down the type-name list in this exact order:

  1. the "default" specified type-name indicated by the collation
  2. the type named "standard"
  3. the type named "search"
  4. the first type

then the options, and yes they're all squished together because that's just the vibe here:

  • -a<alt> — this provides the "alt" property to select specific "type".
  • -d<dataDir> — specify the directory that contains the collation files. default value? the program's directory. 💖
  • -o<outputDir> — specify the directory where the generated files will be stored. default value? again, the program's directory. 🎀
  • -t<HaltOnFail> — to execute parser the test suite. the program will execute only the test suite and exit.

<HaltOnFail> may be one of (y, Y, t, T, 1) to halt the execution on the first failing. (five whole accepted values, she's flexible like that ✨)

now, the program expects some files to already be sitting in the <dataDir> folder:

  • UCA_Rules_SHORT.xml
  • allkeys.txt — this is the file allkeys_CLDR.txt renamed to allkeys.txt

these files are in the core.zip file of the CLDR release files. and here's a real one, pay attention: the CLDR version used should be synchronized with the version of the Unicode version used — for example, for Unicode 7 it will be CLDR 26. (the original page spells it Uniocde 7, and honestly? slay, we're leaving that exactly as it is. 💀) the CLDR files are provided by the Unicode Consortium at http://cldr.unicode.org/index/downloads

🔁 ok and now it does it AGAIN — illegal option -- e

genuinely the same energy, bestie. she's back:

/build/fpc-gpPkVv/fpc-3.2.2+dfsg/debian/tmp/usr/bin/cldrparser-3.2.2: illegal option -- e

and then:

This program creates pascal units from CLDR's collation files for usage with the FreePascal Native Unicode Manager.
Usage : cldrparser <collationFileName> [<typeName>] [-a<alt>] [-d<dataDir>] [-o<outputDir>] [-t<HaltOnFail>]

where :

  • collationFileName — the target file.
  • typeName — optional, the collation's type-name to be parse.

no typeName? default type-name gets chosen from the list, in this order:

  1. the "default" specified type-name indicated by the collation
  2. the type named "standard"
  3. the type named "search"
  4. the first type
  • -a<alt> — provides the "alt" property to select specific "type".
  • -d<dataDir> — the directory containing the collation files. default = the program's directory.
  • -o<outputDir> — where the generated files get stored. default = the program's directory.
  • -t<HaltOnFail> — execute the parser's test suite; it runs only the test suite and exits.

<HaltOnFail> may be one of (y, Y, t, T, 1) to halt the execution on the first failing.

files it wants chilling in <dataDir>:

  • UCA_Rules_SHORT.xml
  • allkeys.txt — this is the file allkeys_CLDR.txt renamed to allkeys.txt

they're inside the core.zip file of the CLDR release files, and the CLDR version used should be synchronized with the version of the Unicode version used — e.g. for Unicode 7 it'll be CLDR 26. 🌸 CLDR files come from the Unicode Consortium at http://cldr.unicode.org/index/downloads

🔁 and AGAIN, illegal option -- l

at this point it's giving loop error energy but we keep going:

/build/fpc-gpPkVv/fpc-3.2.2+dfsg/debian/tmp/usr/bin/cldrparser-3.2.2: illegal option -- l

This program creates pascal units from CLDR's collation files for usage with the FreePascal Native Unicode Manager.
Usage : cldrparser <collationFileName> [<typeName>] [-a<alt>] [-d<dataDir>] [-o<outputDir>] [-t<HaltOnFail>]

where :

  • collationFileName — specify the target file.
  • typeName — optional, specify the collation's type-name to be parse.

if that argument isn't supplied, a default type-name is chosen from the type-name list in the following order:

  1. the "default" specified type-name indicated by the collation
  2. the type named "standard"
  3. the type named "search"
  4. the first type
  • -a<alt> — this provides the "alt" property to select specific "type".
  • -d<dataDir> — the directory containing the collation files. default value is the program's directory.
  • -o<outputDir> — where generated files will be stored. default value is the program's directory.
  • -t<HaltOnFail> — runs the test suite; only the test suite executes, then it exits.

<HaltOnFail> may be one of (y, Y, t, T, 1) to halt the execution on the first failing. ⭐

files needed in <dataDir>:

  • UCA_Rules_SHORT.xml
  • allkeys.txt — this is the file allkeys_CLDR.txt renamed to allkeys.txt

these are in core.zip from the CLDR release files. the CLDR version used should be synchronized with the version of the Unicode version used — for example, for Unicode 7 it will be CLDR 26. 💜 the Unicode Consortium provides the CLDR files at http://cldr.unicode.org/index/downloads

🔁 bestie. illegal option -- p. it's happening. again.

/build/fpc-gpPkVv/fpc-3.2.2+dfsg/debian/tmp/usr/bin/cldrparser-3.2.2: illegal option -- p

This program creates pascal units from CLDR's collation files for usage with the FreePascal Native Unicode Manager.
Usage : cldrparser <collationFileName> [<typeName>] [-a<alt>] [-d<dataDir>] [-o<outputDir>] [-t<HaltOnFail>]

where :

  • collationFileName — the target file to specify.
  • typeName — optional, the collation's type-name to be parse.

if you skip typeName, a default type-name gets chosen from the type-name list in the following order:

  1. the "default" specified type-name indicated by the collation
  2. the type named "standard"
  3. the type named "search"
  4. the first type
  • -a<alt> — provides the "alt" property to select a specific "type".
  • -d<dataDir> — the directory containing the collation files; default value is the program's directory.
  • -o<outputDir> — the directory where generated files will be stored; default value is the program's directory.
  • -t<HaltOnFail> — execute the parser's test suite. the program executes only the test suite and exits.

<HaltOnFail> may be one of (y, Y, t, T, 1) to halt the execution on the first failing. 💅

what it expects sitting in <dataDir>:

  • UCA_Rules_SHORT.xml
  • allkeys.txt — this is the file allkeys_CLDR.txt renamed to allkeys.txt

both live in the core.zip file of the CLDR release files. the CLDR version used should be synchronized with the version of the Unicode version used, for example for Unicode 7 it will be CLDR 26. the files are provided by the Unicode Consortium at http://cldr.unicode.org/index/downloads 🦋

🔁 one more time, no error line this round

and then the page just… starts over again, completely clean, no illegal option line this time:

This program creates pascal units from CLDR's collation files for usage with the FreePascal Native Unicode Manager.
Usage : cldrparser <collationFileName> [<typeName>] [-a<alt>] [-d<dataDir>] [-o<outputDir>] [-t<HaltOnFail>]

where :

  • collationFileName — specify the target file.
  • typeName — optional, specify the collation's type-name to be parse.

if this argument is not supplied, a default type-name is chosen from the type-name list in the following order:

  1. the "default" specified type-name indicated by the collation
  2. the type named "standard"
  3. the type named "search"
  4. the first type
  • -a<alt> — this provides the "alt" property to select specific "type".
  • -d<dataDir> — specify the directory that contains the collation files. the default value is the program's directory.
  • -o<outputDir> — specify the directory where the generated files will be stored. the default value is the program's directory.
  • -t<HaltOnFail> — to execute parser the test suite. the program will execute only the test suite and exit.

<HaltOnFail> may be one of (y, Y, t, T, 1) to halt the execution on the first failing.

and then — and I cannot stress this enough — the page cuts off mid-sentence, right here:

The program expects some files to be present in the <dataDir> folder :

…and that's where part 1 ends. 💀 part 2 is coming, don't touch that dial. 🍓

  • UCA_Rules_SHORT.xml · allkeys.txt — okay bestie, this is the file, and no I'm not being cryptic: allkeys_CLDR.txt gets renamed to allkeys.txt 🎀 so that's the whole glow-up 💅

So where do these even live? They're bundled up inside the core.zip file of the CLDR release files 🦋 that's it, that's the zip.

And the sync tea ☕ the CLDR version you're using should be synchronized with the version of the Unicode version you're using — for example, for Unicode 7 it'll be CLDR 26. Yes this is a whole matching-sets situation, don't mix and match, the vibes will be off 😭

The CLDR files are provided by the Unicode Consortium at http://cldr.unicode.org/index/downloads 🌈 go get 'em, king 👑

✨ SEE ALSO ✨

The full documentation for cldrparser-3.2.2 is maintained as a Texinfo manual 📖 bestie this is the main character doc, the one with everything.

If the info and cldrparser-3.2.2 programs are properly installed at your site, the command

info cldrparser-3.2.2

should give you access to the complete manual 🫶 run it and let it cook 🔥

And that's the whole page, bestie — cldrparser-3.2.2, July 2026, CLDRPARSER-3.2.2(1). Periodt 💖✨ go parse something iconic 🦋👑

📦 where this page comes from