From: Harshula <harshula@gmail.com>
To: libc-locales@sources.redhat.com
Cc: Pravin S <pravin.d.s@gmail.com>
Subject: QUESTION: LC_COLLATE minimal requirements?
Date: Tue, 14 Oct 2008 08:06:00 -0000 [thread overview]
Message-ID: <1223826729.4898.72.camel@B1.HOME> (raw)
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
next reply other threads:[~2008-10-14 8:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 8:06 Harshula [this message]
2008-10-14 8:06 ` Pravin S
2008-10-14 21:56 ` Ulrich Drepper
2008-10-19 16:40 ` Harshula
2008-10-19 18:01 ` Ulrich Drepper
2008-10-20 7:11 ` Pravin S
2008-10-21 13:03 ` Harshula
2008-10-22 6:22 ` Pravin S
2008-10-14 12:23 ` Keld Jørn Simonsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1223826729.4898.72.camel@B1.HOME \
--to=harshula@gmail.com \
--cc=libc-locales@sources.redhat.com \
--cc=pravin.d.s@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).