public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "keld at keldix dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/14095] Review / update collation data from Unicode / ISO 14651
Date: Wed, 01 Jul 2015 08:02:00 -0000	[thread overview]
Message-ID: <bug-14095-716-wNiwpSKOrn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14095-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=14095

--- Comment #6 from keld at keldix dot com <keld at keldix dot com> ---
On Tue, Jun 30, 2015 at 04:03:54PM +0000, joseph at codesourcery dot com wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=14095
> 
> --- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
> On Tue, 30 Jun 2015, keld at keldix dot com wrote:
> 
> > I am willing to contribute with a look on the different issues.
> 
> That would be very helpful, thanks!  The first question would probably be 
> where the original iso14651_t1 file (added in commit 
> b0a3e2e6238f4846bc7a99145d2721b8d5b5ec31 in the history repository) came 
> from; if we can reproduce it from old ISO 14651 data, we can hopefully 
> build a corresponding file from current ISO 14651 data - and then start to 
> understand, for all the changes made to the data over the past 15 years, 
> which of them are still relevant and desirable given current ISO 14651 / 
> Unicode data as a base, and what the right way is to handle those changes.

It is my plan to work with the editor of 14651 on making the 14651
data directly useable with glibc. This is not currently the case
and we know it.

Keld

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2015-07-01  8:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 21:06 [Bug localedata/14095] New: " jsm28 at gcc dot gnu.org
2013-11-26 17:09 ` [Bug localedata/14095] " myllynen at redhat dot com
2014-02-18 10:12 ` pravin.d.s at gmail dot com
2014-06-25 12:08 ` fweimer at redhat dot com
2014-10-10 21:50 ` maiku.fabian at gmail dot com
2015-06-30  5:09 ` pabs3 at bonedaddy dot net
2015-06-30 13:40 ` joseph at codesourcery dot com
2015-06-30 15:29   ` Keld Simonsen
2015-06-30 13:45 ` carlos at redhat dot com
2015-06-30 15:30 ` keld at keldix dot com
2015-06-30 21:03 ` joseph at codesourcery dot com
2015-07-01  7:57   ` Keld Simonsen
2015-07-01  8:02 ` keld at keldix dot com [this message]
2016-02-19 10:46 ` vapier at gentoo dot org
2016-02-19 17:18 ` joseph at codesourcery dot com
2017-12-14 16:53 ` maiku.fabian at gmail dot com
2017-12-14 16:58 ` maiku.fabian at gmail dot com
2018-01-25 10:41 ` maiku.fabian at gmail dot com
2018-02-27 16:55 ` cvs-commit at gcc dot gnu.org
2018-02-28 14:11 ` maiku.fabian at gmail dot com
2018-03-02 12:59 ` cvs-commit at gcc dot gnu.org
2018-03-31 12:32 ` jeremip11 at gmail dot com
2018-07-09 12:01 ` fweimer at redhat dot com
2018-08-01  5:58 ` cvs-commit at gcc dot gnu.org

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=bug-14095-716-wNiwpSKOrn@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@sourceware.org \
    /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).