This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales project.
Re: QUESTION: LC_COLLATE minimal requirements?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Pravin S wrote:
>> Q1) Is it a requirement to use the collating-symbol keyword to define
>> ALL symbols? If not, is this patch sufficient and acceptable for glibc?
>> http://cvs.savannah.gnu.org/viewvc/sinhala/patches/iso14651_t1_common-glibc.patch?root=sinhala&view=log
It's better to follow the example of the other languages. This results
in better tables. And it's trivial. Just use
<U0DF4> <U0DF4>;<BAS>;<MIN>;IGNORE
etc
>> Q2) Instead of explicitly listing all the characters in order, is it
>> possible to use the reorder-after keyword to only define variations to
>> the DUCET?
I have no idea what this means? Each Unicode position can only appear
once in the entire file. If you add a new language with new characters,
then just put them in the right order. If you need to change the
collation for existing characters, then you must use reorder_after the
the locale description outside the collation tables themselves.
>> Q3) I couldn't find any documentation on:
>>
>> translit_start
>> include "translit_combining";""
>> translit_end
Just look at the files. There is no magic. It's a 1:N mapping.
- --
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkj030AACgkQ2ijCOnn/RHSBKACeIdqAhld7yAS4UUKZOye3QzYy
NakAn3hwJtj9Ft8V3x9hz09f2fQIj0RQ
=uJHD
-----END PGP SIGNATURE-----