From: Carlos O'Donell <carlos@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Rafal Luzynski <digitalfreak@lingonborough.com>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>
Subject: Re: glibc 2.29 - Winter is coming...
Date: Fri, 4 Jan 2019 16:25:19 -0500 [thread overview]
Message-ID: <2385ce81-2711-957f-b3ad-530bb1e101df@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1901032054490.20350@digraph.polyomino.org.uk>
On 1/3/19 3:58 PM, Joseph Myers wrote:
> On Thu, 3 Jan 2019, Carlos O'Donell wrote:
>
>> The new Era name will likely have to be backported to all the active
>> open stable branches so they can display the new Era name.
>
> Presumably that includes the character properties for U+32FF? (Does
> anything in glibc care about the to-be-announced compatibility
> decomposition that's the reason Unicode 12.1 will be needed
> <https://www.unicode.org/L2/L2018/18220-u121planning.txt> or is glibc only
> concerned with character properties that are already known?)
Yes, it should include the character properties for U+32FF (if possible).
Yes we care about compatibility decomposition when computing the
transliterated version of the Era name (see
localedata/unicode-gen/gen_translit_compat.py (compatibility_decompose)).
I'm going to handle the Era name change myself when it arrives unless
someome beats me to it, we need it in RHEL.
I will limit the backport as much as I can to reduce risk.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-01-04 21:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:28 glibc 2.29 - Winter is coming Siddhesh Poyarekar
2019-01-02 10:59 ` Florian Weimer
2019-01-02 11:29 ` Siddhesh Poyarekar
2019-01-02 11:52 ` Rafal Luzynski
2019-01-02 18:24 ` Siddhesh Poyarekar
2019-01-03 0:20 ` Rafal Luzynski
2019-01-03 14:32 ` Carlos O'Donell
2019-01-03 20:58 ` Joseph Myers
2019-01-04 21:25 ` Carlos O'Donell [this message]
2019-01-07 18:59 ` Florian Weimer
2019-01-02 13:11 ` Gabriel F. T. Gomes
2019-01-02 13:16 ` Florian Weimer
2019-01-02 13:47 ` Siddhesh Poyarekar
2019-01-02 16:02 ` Gabriel F. T. Gomes
2019-01-08 13:33 ` Szabolcs Nagy
2019-01-08 14:16 ` Carlos O'Donell
2019-01-08 14:21 ` Szabolcs Nagy
2019-01-08 16:50 ` Carlos O'Donell
2019-01-09 10:50 ` Ramana Radhakrishnan
2019-01-09 16:03 ` Carlos O'Donell
[not found] ` <BL0PR01MB4593D75E9376CC15EE8CA24AF7990@BL0PR01MB4593.prod.exchangelabs.com>
2019-01-23 14:07 ` Carlos O'Donell
2019-01-09 5:48 ` Siddhesh Poyarekar
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2385ce81-2711-957f-b3ad-530bb1e101df@redhat.com \
--to=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).