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?
- From: "Pravin S" <pravin dot d dot s at gmail dot com>
- To: Harshula <harshula at gmail dot com>
- Cc: libc-locales at sources dot redhat dot com, "Ulrich Drepper" <drepper at redhat dot com>
- Date: Tue, 14 Oct 2008 11:11:21 +0530
- Subject: Re: QUESTION: LC_COLLATE minimal requirements?
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=LyiF5gR+pfBiJHi4bMj1CsdPDbyVKS9Q4+4i7ujcAOY=; b=qh1o65fxYEClgFJbHQlGhxHW8T60nsDDeJW0UlX6LKQ4tQy+If/nB//dmfoHA4yxBp Z8TvI5SuVgpSiaA4qpEpsqUKgVIfTZ0w3WUaLo7hc0DWZyz9XS9bQImgP9UE90ILkLQz iHClAHmHahg3KST05zT9TpfERMHe0o484nxaQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=fkdiCBjKxAr5R6Da2HlC9Uw2N88HHO9X7JRzfZqG4m5bPs9isnVLrYtRHiUICYHnNI NCNfIWWgTIZs9aCmZC0Hd/xxGpjHbI34BB8ERUwzzVx5yr0GbfKcdKoLhC0jCmtJVWEL VAWWVhuzWhztCn6D/cfk/j3kgDR1F1tPijudc=
- References: <1223826729.4898.72.camel@B1.HOME>
2008/10/12 Harshula <harshula@gmail.com>:
> Hi,
>
> I was unable to find much documentation on LC_COLLATE except for [1].
> Hence I have a few questions.
>
> Firstly, some background information. The Sinhala collation sequence
> (SLS1134) is relatively simple.
>
> * It does not have multiple characters mapping to a single
> collation element.
> * It does not consider composed and decomposed dependent vowels as
> equivalent [2].
> * It does not have to deal with secondary and tertiary weights.
> * It has a few simple tailoring rules [3] that need to be applied to the
> DUCET [4].
>
>
> 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
>
> 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?
>
> Q3) I couldn't find any documentation on:
>
> translit_start
> include "translit_combining";""
> translit_end
>
> /usr/share/i18n/locales/translit_combining
> ------------------------------------------
> % SINHALA VOWEL SIGN DIGA KOMBUVA
> <U0DDA> "<U0DD9><U0DCA>"
> % SINHALA VOWEL SIGN KOMBUVA HAA AELA-PILLA
> <U0DDC> "<U0DD9><U0DCF>"
> % SINHALA VOWEL SIGN KOMBUVA HAA DIGA AELA-PILLA
> <U0DDD> "<U0DDC><U0DCA>"
> % SINHALA VOWEL SIGN KOMBUVA HAA GAYANUKITTA
> <U0DDE> "<U0DD9><U0DDF>"
> ------------------------------------------
>
> Does translit_start have an affect on LC_COLLATE?
>
> Thanks,
> #
>
> [1]
> http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html
>
> [2]
> http://sourceforge.net/mailarchive/forum.php?thread_name=1223803982.4898.16.camel%40B1.HOME&forum_name=sinhala-technical
>
> [3]
> http://www.nongnu.org/sinhala/doc/howto/sinhala-howto.html#DEV-DATABASES
>
> [4] http://unicode.org/Public/UCA/latest/allkeys.txt
>
>
Adding Ulrich in cc list,
Thanks & Regards,
----------------------
Pravin Satpute