X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/128b8f63886c8a5099e1657b5c60b5f43cd21e1b..ae5db6d19f3d85fdd5e7bd4c12be28fa3f15fc43:/linux/glibc/howto.html diff --git a/linux/glibc/howto.html b/linux/glibc/howto.html index 9af9aed353..7b68909fb8 100644 --- a/linux/glibc/howto.html +++ b/linux/glibc/howto.html @@ -35,7 +35,12 @@ 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.
+ included in glibc. If one can't convince the ISO 639 + maintainers that your language exists (and thus need a + language code), the glibc maintainers will refuse to add the + locale. In addition, the glibc maintainers seem to refuse + "artificial languages" like Esperanto and Lojban, even if they + got a ISO 639 code.Little is known about the requirements for the naming of modifiers. The following modifiers are currently used: @@ -81,20 +86,29 @@
One should avoid cut-n-paste when possible, and instead use + the copy statement to include sections from locales + with identical content.
The category entries are references to the standard used when + writing the given section. The standard refs should have + quotes around them, and should not use the <U#> + notation. They should normally look something like this:
- - quotes around the text - - - no <U#>, use normal ASCII ++category "i18n:1997";LC_IDENTIFICATION +
Then yesexpr and noexpr entries should have the form + ^[yY<extra>] and ^[nN<extra>], + without 0 and 1 and without trailing ".*". The + reason is to make sure the expressions have the same form as + the expressions used in the C/POSIX locale (^[yY] and + ^[nN]).
I've made a small tool check-locale + capable of detecting a few common mistakes with locales
@@ -133,7 +150,7 @@ Petter Reinholdtsen -Last modified: Mon Aug 9 01:09:09 CEST 2004 +Last modified: Mon Dec 20 20:17:59 CET 2004