X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/ce5a4ad36f761fdc75d5d72600b021e231c8f19a..6a79add34b0b1c6dd9e27c6af3c7f6fe2b23438d:/linux/glibc/howto.html diff --git a/linux/glibc/howto.html b/linux/glibc/howto.html new file mode 100644 index 0000000000..641827d4e5 --- /dev/null +++ b/linux/glibc/howto.html @@ -0,0 +1,96 @@ + + + + How to write a GNU libc locale + + + + + + + + +
+

How to write a GNU libc locale

+
+ +
+ Back +
+ +
+ +

This is a draft document explaining how to write locale files + for GNU libc. It will not go into details, but reference + specifications. It will on the other hand mention some of the + pitfalls, and try to document the current practice.

+ +

How to choose the locale file name

+ +

Locale names consist of three parts. The language code, the + country/region code, and the optional modifier. The format is + language_REGION@modifier. The language code is a code from + ISO 639. The two-letter code is prefered, but a three letter + code is accepted if no two-letter code is available. The + country/region code is a code from ISO 3166. If the language + or region in question is missing in the ISO standard, one need + to get the ISO standard updated before the locale will be + included in glibc.

+ +

Little is known about the requirements for the naming of + modifiers. The following modifiers are currently used: + abegede, cyrillic, euro and saaho. This might indicate that + lower case letters are prefered in modifier names.

+ + + + +

Category order

+ +

To make it easier to compare locales with each other, I + recommend using the same order for the categories in all + locales. Any order will do, so I picked the order used in most + locales, and decided to recommend this order:

+ +
    +
  1. LC_IDENTIFICATION +
  2. LC_CTYPE +
  3. LC_COLLATE +
  4. LC_MONETARY +
  5. LC_NUMERIC +
  6. LC_TIME +
  7. LC_MESSAGES +
  8. LC_PAPER +
  9. LC_NAME +
  10. LC_ADDRESS +
  11. LC_TELEPHONE +
  12. LC_MEASUREMENT +
+ +

Reuse when possible

+ + - "copy" from existing locales if the content should be identical + +

LD_INDENTIFICATION

+ + - standard refs in the LD_INDENTIFICATION + +

LC_MESSAGES

+ + - yes/no expr should have the form ^[yYnN], without 0 and 1 + +

Standard documents and specifications

+ +
+ +
+
Petter Reinholdtsen
+ + +Last modified: Sat Jul 24 15:19:14 CEST 2004 + + +