public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/18568] Update locale data to Unicode 8.0
Date: Mon, 22 Jun 2015 21:30:00 -0000	[thread overview]
Message-ID: <bug-18568-716-xmOj0Mxi8N@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18568-716@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to Marko Myllynen from comment #1)
> The following Unicode Blog posting provides some comments about required
> implementation changes, however I haven't investigated how relevant these
> are from glibc perspective.

I think for glibc, this has little impact.

> http://blog.unicode.org/2015/03/unicode-80-beta-review.html
> 
> Unicode 8.0.0 comprises several changes which require careful migration in
> implementations, including the conversion of Cherokee to a bicameral script,

That means Cherokee has upper and lower case now, lots of characters
get added to "toupper", "tolower", "totitle" in the "i18n" file.

> a different encoding model for New Tai Lue, and additional character
> repertoire.

Many New Tai Lue characters which were combining characters before are
not combining characters anymore.

> Implementers need to change code and check assumptions regarding
> case mappings New Tai Lue syllables, Han character ranges, and confusables.

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

  parent reply	other threads:[~2015-06-22 21:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20 22:54 [Bug localedata/18568] New: " jsm28 at gcc dot gnu.org
2015-06-22  5:07 ` [Bug localedata/18568] " myllynen at redhat dot com
2015-06-22 21:30 ` maiku.fabian at gmail dot com [this message]
2015-06-22 21:30 ` maiku.fabian at gmail dot com
2015-06-24  9:59 ` pabs3 at bonedaddy dot net
2015-06-24 14:31 ` joseph at codesourcery dot com
2015-06-26  3:36 ` pabs3 at bonedaddy dot net
2015-06-26  7:31 ` schwab@linux-m68k.org
2015-06-27  4:13 ` pabs3 at bonedaddy dot net
2015-06-29 20:09 ` carlos at redhat dot com
2015-06-29 20:29   ` Keld Simonsen
2015-06-29 20:48 ` joseph at codesourcery dot com
2015-06-29 20:48 ` keld at keldix dot com
2015-06-30  5:10 ` pabs3 at bonedaddy dot net
2015-06-30 13:54 ` carlos at redhat dot com
2015-07-01  6:45 ` maiku.fabian at gmail dot com
2015-11-21 21:30 ` fweimer at redhat dot com
2015-11-24  6:29 ` maiku.fabian at gmail dot com
2015-12-10 21:26 ` carlos at redhat dot com

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-18568-716-xmOj0Mxi8N@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).