linux/glibc/howto.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
   2 <html lang="en">
   3   <head>
   4     <title>How to write a GNU libc locale</title>
   5     <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   6     <meta http-equiv="Content-Language" content="en">
   7     <link rel="stylesheet" type="text/css" href="http://i18n.skolelinux.no/stilsett.css" id="nn1">
   8     <link rel="stylesheet" type="text/css" href="http://i18n.skolelinux.no/utskrift.css" media="print" id="nn2">
   9
  10   </head>
  11
  12   <body>
  13     <div class="topp">
  14     <h1>How to write a GNU libc locale</h1>
  15     </div>
  16
  17     <div class="meny">
  18       <a href="./">Back</a>
  19     </div>
  20
  21     <div class="hovuddel">
  22
  23     <p>This is a draft document explaining how to write locale files
  24       for GNU libc.  It will not go into details, but reference
  25       specifications.  It will on the other hand mention some of the
  26       pitfalls, and try to document the current practice.</p>
  27
  28     <h2>How to choose the locale file name</h2>
  29
  30       <p>Locale names consist of three parts.  The language code, the
  31         country/region code, and the optional modifier.  The format is
  32         language_REGION@modifier.  The language code is a code from
  33         ISO 639.  The two-letter code is prefered, but a three letter
  34         code is accepted if no two-letter code is available.  The
  35         country/region code is a code from ISO 3166.  If the language
  36         or region in question is missing in the ISO standard, one need
  37         to get the ISO standard updated before the locale will be
  38         included in glibc.  If one can't convince the ISO 639
  39         maintainers that your language exists (and thus need a
  40         language code), the glibc maintainers will refuse to add the
  41         locale.  In addition, the glibc maintainers seem to refuse
  42         "artificial languages" like Esperanto and Lojban, even if they
  43         got a ISO 639 code.</p>
  44
  45       <p>Little is known about the requirements for the naming of
  46         modifiers.  The following modifiers are currently used:
  47         abegede, cyrillic, euro and saaho.  This might indicate that
  48         lower case letters are prefered in modifier names.</p>
  49
  50       <p>It is recommended to follow RFC 3066 when selecting locale
  51         names.</p>
  52
  53       <ul>
  54
  55         <li><a href="http://www.unicode.org/onlinedat/countries.html">ISO
  56             3166</a></li>
  57
  58         <li><a href="http://www.loc.gov/standards/iso639-2/">ISO 639</a></li>
  59
  60         <li><a href="http://rfc.sunsite.dk/rfc/rfc3066.html"> RFC 3066
  61             - Tags for the Identification of Languages</a></li>
  62
  63       </ul>
  64
  65     <h2>Category order</h2>
  66
  67     <p>To make it easier to compare locales with each other, I
  68       recommend using the same order for the categories in all
  69       locales.  Any order will do, so I picked the order used in most
  70       locales, and decided to recommend this order:</p>
  71
  72     <ol>
  73       <li>LC_IDENTIFICATION
  74       <li>LC_CTYPE
  75       <li>LC_COLLATE
  76       <li>LC_MONETARY
  77       <li>LC_NUMERIC
  78       <li>LC_TIME
  79       <li>LC_MESSAGES
  80       <li>LC_PAPER
  81       <li>LC_NAME
  82       <li>LC_ADDRESS
  83       <li>LC_TELEPHONE
  84       <li>LC_MEASUREMENT
  85     </ol>
  86
  87     <h2>Reuse when possible</h2>
  88
  89     - "copy" from existing locales if the content should be identical
  90
  91     <h2>LD_IDENTIFICATION</h2>
  92
  93     - standard refs in the LD_IDENTIFICATION
  94
  95     - quotes around the text
  96
  97     - no &lt;U#&gt;, use normal ASCII
  98
  99     <h2>LC_MESSAGES</h2>
 100
 101     - yes/no expr should have the form ^[yYnN<extra>], without 0 and 1
 102       and without trailing ".*".
 103
 104     <h2>Standard documents and specifications</h2>
 105
 106     <h2>Testing the new locale file</h2>
 107
 108         <p>To test a new locale on a test machine, do the
 109         following:</p>
 110
 111         <ul>
 112
 113           <li>Copy the new locale to
 114             <tt>/usr/share/i18n/locales/<em>filename</em></tt></li>
 115
 116           <li>Run <tt>localedef -i <em>inputfile</em> -c -f
 117               <em>charset<em> <em>locale</em></tt> to generate a
 118             binary locale file in
 119             <tt>/usr/lib/locale/<em>locale</em>/</tt></li>
 120
 121           <li>Test it using LANG=<em>locale</em>, for example by
 122             running <tt>date</tt></li>
 123
 124         </ul>
 125
 126         <p>Example, generating a new <tt>de_DE@euro</tt> locale using
 127           the ISO-8859-15 charset and save it as 'de_DE':</p>
 128
 129         <pre>
 130           cp de_DE@euro /usr/share/i18n/locales/de_DE@euro
 131           localedef -i de_DE@euro -c -f ISO-8859-15 de_DE
 132           LANG=de_DE date
 133         </pre>
 134
 135     </div>
 136
 137     <hr>
 138     <address><a href="mailto:pere@hungry.com">Petter Reinholdtsen</a></address>
 139 <!-- Created: Sun Mar 21 18:14:42 CET 2004 -->
 140 <!-- hhmts start -->
 141 Last modified: Mon Aug  9 08:30:26 CEST 2004
 142 <!-- hhmts end -->
 143   </body>
 144 </html>