Jeu George writes:
> > Once you have done "localedef -i fr -f UTF-8 fr.UTF-8", the fr.UTF-8
> > directory should contain the LC_COLLATE etc. files as well.
>
> what does this statement do exactly do
"man localedef".
> where do we actually mention the collation order. Is it that we write the
> order os character as they are supposed to be in a file within the
> LC_COLLATE dir. If yes how is this done, ie. what statement do you use to
> make the actuall comparison. If no, why are this LC_COLLATE LC_CTYPE etc
> made as dir's , why not as files.
As an application writer, you can assume that the necessary locales
supported by the OS come bundled with the OS.
As a user, on Linux, you can always install all glibc-supported
locales by compiling glibc and doing
# make localedata/install-locales
If a locale you need (let's say, Thai or India) is not supported by
glibc, and you want to write it yourself, you put the description of
the locale into /usr/share/locale/<locale>/ and use the localedef
utility to compile it into a set of files into /usr/lib/locale/<locale>/.
The syntax of these description files is described in SUSV2 (for the
easier parts) and the ISO 14652 draft, which you can get somewhere on
the web. The LC_COLLATE description format is quite complicated.
Remember that multibyte locales are not supported in glibc-2.1 yet;
they will be in glibc-2.2.
Bruno
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
