From: "Pravin S" <pravin.d.s@gmail.com>
To: Harshula <harshula@gmail.com>
Cc: "Ulrich Drepper" <drepper@redhat.com>, libc-locales@sources.redhat.com
Subject: Re: QUESTION: LC_COLLATE minimal requirements?
Date: Mon, 20 Oct 2008 07:11:00 -0000 [thread overview]
Message-ID: <764372c80810192350u205d1f9bnf0597031d089a05b@mail.gmail.com> (raw)
In-Reply-To: <1224429227.18677.18.camel@B1.HOME>
Hi All,
2008/10/19 Harshula <harshula@gmail.com>:
> Hi Ulrich,
>
> On Tue, 2008-10-14 at 11:04 -0700, Ulrich Drepper 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
>
> Thanks, I've made the changes.
>
> Patch:
> http://cvs.savannah.gnu.org/viewvc/sinhala/patches/iso14651_t1_common-glibc.patch?root=sinhala&view=log
>
> Testcase:
> http://cvs.savannah.gnu.org/viewvc/sinhala/patches/mysql-data-sinhala.txt?root=sinhala&view=log
>
> Correct output from 'sort':
> http://cvs.savannah.gnu.org/viewvc/sinhala/patches/glibc-collation-correct.txt?root=sinhala&view=log
>
>
Harshula I think,
It will be nice if you filed bug @
http://sourceware.org/bugzilla/enter_bug.cgi?product=glibc
and submit patch there, it will be good for tracking
Thanks & Regards,
----------------------
Pravin Satpute
next prev parent reply other threads:[~2008-10-20 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 8:06 Harshula
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 [this message]
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=764372c80810192350u205d1f9bnf0597031d089a05b@mail.gmail.com \
--to=pravin.d.s@gmail.com \
--cc=drepper@redhat.com \
--cc=harshula@gmail.com \
--cc=libc-locales@sources.redhat.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).