glibc 2.29 - Winter is coming...

[Carlos O'Donell]

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.