public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "egmont at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/22387] Replace unicode sequences <Uxxxx> for characters inside the ASCII printable range
Date: Tue, 14 Nov 2017 13:19:00 -0000	[thread overview]
Message-ID: <bug-22387-716-UUCdi8OKcJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22387-716@http.sourceware.org/bugzilla/>

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

--- Comment #27 from Egmont Koblinger <egmont at gmail dot com> ---
(In reply to keld@keldix.com from comment #25)

> This commit is highly problematic, damaging the portablilty of glibc locales.

If this kind of portability is really a concern, someone could some up with a
script that converts from the new version to the old one. It could even be
integrated with the build system to the level where these generated files are
actually placed under BUILD and then further processed.

I wish the current change even pushed it further, towards raw UTF-8 at least
for printable and "non-problematic" (to some vague, arbitrary definition)
characters.

I have on a few occasions made some minor edits to effected parts of a locale
file, dealing with the <Uxxxx> notation was a nightmare. Working with a string
like "h<U00E9>tf<U0151>" is already much better than
"<U0068><U00E9><U0074><U0066><U0151>", but seeing "hétfő" would be ideal.

Source code is meant to be human-readable, which all these <Uxxxx>s is most
certainly not.

There's a reason people write code like
  printf("Hello world!\n");
and not
  printf("\x48\x65\x6c\x6c\x6f\x20\x77\x6f\x72\x6c\x64\x21\x0a");

If for whatever reason the latter, hard-to-read (and hard-to-write) form is
required, it should be auto-generated from the former, easy-to-read (and
easy-to-write) one.

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

  parent reply	other threads:[~2017-11-14 13:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 14:00 [Bug localedata/22387] New: " claude at 2xlibre dot net
2017-11-02 14:15 ` [Bug localedata/22387] " claude at 2xlibre dot net
2017-11-02 23:34   ` Keld Simonsen
2017-11-02 16:54 ` maiku.fabian at gmail dot com
2017-11-02 17:00 ` maiku.fabian at gmail dot com
2017-11-02 17:06 ` claude at 2xlibre dot net
2017-11-02 17:21 ` claude at 2xlibre dot net
2017-11-02 17:38 ` schwab@linux-m68k.org
2017-11-02 20:40 ` egmont at gmail dot com
2017-11-02 23:34 ` keld at keldix dot com
2017-11-03  3:12 ` carlos at redhat dot com
2017-11-07 23:54   ` Keld Simonsen
2017-11-08 19:59   ` Keld Simonsen
2017-11-03  6:49 ` schwab@linux-m68k.org
2017-11-03  9:52 ` egmont at gmail dot com
2017-11-03  9:56 ` egmont at gmail dot com
2017-11-09 10:18   ` Keld Simonsen
2017-11-03 15:43 ` maiku.fabian at gmail dot com
2017-11-03 15:51 ` egmont at gmail dot com
2017-11-03 16:49 ` joseph at codesourcery dot com
2017-11-06 13:23 ` claude at 2xlibre dot net
2017-11-06 13:26 ` claude at 2xlibre dot net
2017-11-07 15:12 ` claude at 2xlibre dot net
2017-11-07 16:57 ` piotrdrag at gmail dot com
2017-11-07 23:54 ` keld at keldix dot com
2017-11-08 20:00 ` keld at keldix dot com
2017-11-09 10:19 ` keld at keldix dot com
2017-11-09 16:31 ` joseph at codesourcery dot com
2017-11-14  8:11 ` cvs-commit at gcc dot gnu.org
2017-11-14  8:13 ` maiku.fabian at gmail dot com
2017-11-14  8:17 ` claude at 2xlibre dot net
2017-11-14 13:02   ` Keld Simonsen
2017-11-14 13:02 ` keld at keldix dot com
2017-11-14 13:06   ` Keld Simonsen
2017-11-14 13:07 ` keld at keldix dot com
2017-11-14 13:19 ` egmont at gmail dot com [this message]
2017-11-14 20:25 ` jwilk at jwilk dot net
2017-11-14 23:32 ` carlos at redhat dot com
2017-11-15 10:15 ` maiku.fabian at gmail dot com
2017-11-16 23:39   ` Keld Simonsen
2017-11-15 10:36 ` schwab@linux-m68k.org
2017-11-16 23:39 ` keld at keldix 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-22387-716-UUCdi8OKcJ@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).