X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/3c6c13a4fc3b70af007e7d74f4fc407c72e44329..d82bc652caa79a004e27bc591fef3fed5d68fb03:/linux/glibc/howto.html diff --git a/linux/glibc/howto.html b/linux/glibc/howto.html index f3b604191c..a7a18a7599 100644 --- a/linux/glibc/howto.html +++ b/linux/glibc/howto.html @@ -1,13 +1,24 @@ - + How to write a GNU libc locale + + + + + +

How to write a GNU libc locale

+
+ +
+ Back +
-
by Petter Reinholdtsen
+

This is a draft document explaining how to write locale files for GNU libc. It will not go into details, but reference @@ -16,7 +27,35 @@

How to choose the locale file name

- - how to choose the 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.

+ +

It is recommended to follow RFC 3066 when selecting locale + names.

+ +

Category order

@@ -44,9 +83,9 @@ - "copy" from existing locales if the content should be identical -

LD_INDENTIFICATION

+

LD_IDENTIFICATION

- - standard refs in the LD_INDENTIFICATION + - standard refs in the LD_IDENTIFICATION

LC_MESSAGES

@@ -54,11 +93,13 @@

Standard documents and specifications

+
+
Petter Reinholdtsen
-Last modified: Sat May 15 11:56:09 CEST 2004 +Last modified: Tue Jul 27 09:07:23 CEST 2004