]> git.ipfire.org Git - thirdparty/glibc.git/blame - localedata/README
powerpc: Remove optimized finite
[thirdparty/glibc.git] / localedata / README
CommitLineData
f5f52655
UD
1 POSIX locale descriptions
2 and
3 POSIX character set descriptions
4
597ce09c
UD
5Ulrich Drepper Time-stamp: <2004/11/27 13:06:54 drepper>
6drepper@redhat.com
f5f52655
UD
7
8
3a17c568
AJ
9This directory contains the data needed to build the locale data files
10to use the internationalization features of the GNU libc.
f5f52655
UD
11
12POSIX.2 describes the `localedef' utility which is part of the GNU libc.
13You need this program to "compile" the locale description in a form
14suitable for fast access by the GNU libc functions. Any compilation is
15based on a given character set.
16
3a17c568
AJ
17Once you run `make install' for the GNU libc the data files are
18automatically installed in the right place, ready for use by the
19`localedef' program.
f5f52655
UD
20
21To compile the locale data files you simply have to decide which locale
22(based on the location and the language) and which character set you
23use. E.g., French speaking Canadians would use the locale `fr_CA' and
24the character set `ISO_8859-1,1987'. Calling `localedef' to get the
25desired data should happen like this:
26
27 localedef -i fr_CA -f ISO-8859-1 fr_CA
28
29This will place the 6 output files in the appropriate directory where
39e16978
UD
30the GNU libc functions can find them. Please note that you need
31permission to write to this directory ($(prefix)/share/locale, where
f5f52655 32$(prefix) is the value you specified while configuring GNU libc). If
39e16978 33you do not have the necessary permissions, you can write the files into an
f5f52655
UD
34arbitrary directory by giving a path including a '/' character instead
35of `fr_CA'. E.g., to put the new files in a subdirectory of the
36current directory simply use
37
38 localedef -i fr_CA -f ISO-8859-1 ./fr_CA
39
40How to use these data files is described in the GNU libc manual,
41especially in the section describing the `setlocale' function.
42
597ce09c 43All problems should be reported using
f5f52655 44
a306c790 45 https://sourceware.org/bugzilla/
f5f52655
UD
46
47
48One more note: the `POSIX' locale definition is not meant to be used
49as an input file for `localedef'. It is rather there to show the
50values with are built in the libc binaries as default values when no
51legal locale is found or the "C" or "POSIX" locale is selected.
52
53
54 The collation test suite
55 ########################
56
57This package also contains a (beginning of a) test suite for the
58collation functions in the GNU libc. The files are provided sorted.
59The test program shuffles the lines and sort them afterwards.
60
61Some of the files are provided in 8bit form, i.e., not only ASCII
62characters. So the tools you use to process the files should be 8bit
63clean.
64
65To run the test program the appropriate locale information must be
66installed. Therefore the localedef program is used to generate this
67data used the locale and charmap description files contained here.
68Since we cannot run the localedef program in case of cross-compilation
69no tests at all are performed.
70
71
72~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
73Local Variables:
74 mode:text
75 eval:(load-library "time-stamp")
76 eval:(make-local-variable 'write-file-hooks)
77 eval:(add-hook 'write-file-hooks 'time-stamp)
78 eval:(setq time-stamp-format '(time-stamp-yyyy/mm/dd time-stamp-hh:mm:ss user-login-name))
79End: