X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/63885cf4c17a46e172d36e701f9258b0878cb76c..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 @@ + + +
+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.
+ +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.
+ + + + +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:
+ +