From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sources.redhat.com
Subject: [Bug localedata/14095] New: Review / update collation data from Unicode / ISO 14651
Date: Thu, 10 May 2012 21:06:00 -0000 [thread overview]
Message-ID: <bug-14095-716@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14095
Bug #: 14095
Summary: Review / update collation data from Unicode / ISO
14651
Product: glibc
Version: 2.15
Status: NEW
Severity: normal
Priority: P2
Component: localedata
AssignedTo: unassigned@sourceware.org
ReportedBy: jsm28@gcc.gnu.org
CC: libc-locales@sources.redhat.com
Classification: Unclassified
The localedata/locales/iso14651_t1_* files are probably, from their names,
originally based on some version of ISO 14651 collation data. They should be
updated if possible to be based on the current Unicode collation data and
algorithms.
http://www.unicode.org/reports/tr10/
Since there have been a lot of changes to these files since the original
addition in
2000-05-24 Ulrich Drepper <drepper@redhat.com>
* locales/iso14651_t1: New file.
it's likely there will be a lot of work to understand how the files relate to
ISO 14651 and what local changes are still relevant.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-05-10 21:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 21:06 jsm28 at gcc dot gnu.org [this message]
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
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@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).