This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales project.
[Bug localedata/22387] Replace unicode sequences <Uxxxx> for characters inside the ASCII printable range
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: libc-locales at sourceware dot org
- Date: Fri, 03 Nov 2017 03:12:25 +0000
- Subject: [Bug localedata/22387] Replace unicode sequences <Uxxxx> for characters inside the ASCII printable range
- Auto-submitted: auto-generated
- References: <bug-22387-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22387
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #8 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to keld@keldix.com from comment #7)
> I think we should not do this, as it would make locales unusable
> with ebcdic encodings. I am also unsure how it will work with utf-16.
Please provide a justification for this requirement to support EBCDIC and
UTF-16, included systems that would be impacted today by this change.
I spoke with Ulrich Drepper directly, and he did point out that the design idea
behind using <Uxxxx> sequences was indeed to support the locales on systems
that had other encodings like EBCDIC, but with the rise of UTF-8 as the defacto
standard, no such systems have really materialized.
> I propose you use better mnemonics for the ascii range, such as <a> for a,
> etc. That is, use the mnemonics defined in the POSIX standard for the ascii
> range.
I disagree strongly with this, why use '<a>' instead of 'a'? Please provide
strong rationale for why we should keep using the <Uxxxx> format.
--
You are receiving this mail because:
You are on the CC list for the bug.