Unicode 9.0.0 has been released recently (2016-06-21).
Here is a patch to update the i18n, tr_TR, UTF-8, and the translit_* files to Unicode 9.0.0.
I have sent this patch to the libc-alpha mailing list already (against current master of glibc).
This patch here is against our current F24 package.
Is it OK to push this to F24 and apply it to master?
On 06/29/2016 05:08 PM, Mike FABIAN wrote:
Is it OK to push this to F24 and apply it to master?
It's odd to apply this to F24 and have a Fedora Change for F25.
I think it's either backportable (non-disruptive) or Change-worthy (potentially disruptive). It can't be both, really.
Florian
On 07/05/2016 02:07 PM, Florian Weimer wrote:
On 06/29/2016 05:08 PM, Mike FABIAN wrote:
Is it OK to push this to F24 and apply it to master?
It's odd to apply this to F24 and have a Fedora Change for F25.
I think it's either backportable (non-disruptive) or Change-worthy (potentially disruptive). It can't be both, really.
These changes are always potentially disruptive.
The patch looks good for Fedora Rawhide.
Please keep F24 using Unicode 8.0.0.
I would like Unicode updates to happen only at release boundaries.
"Carlos O'Donell" carlos@redhat.com さんはかきました:
On 07/05/2016 02:07 PM, Florian Weimer wrote:
On 06/29/2016 05:08 PM, Mike FABIAN wrote:
Is it OK to push this to F24 and apply it to master?
It's odd to apply this to F24 and have a Fedora Change for F25.
I think it's either backportable (non-disruptive) or Change-worthy (potentially disruptive). It can't be both, really.
These changes are always potentially disruptive.
The patch looks good for Fedora Rawhide.
Please keep F24 using Unicode 8.0.0.
I would like Unicode updates to happen only at release boundaries.
Oh, sorry, of course you are right, I intended this for F25 of course. I built it for F24 only for testing on my system, you are right that it should be pushed only to master, i.e. F25.