public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: Florian Weimer <fw@deneb.enyo.de>, Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha@sourceware.org, Mike FABIAN <mfabian@redhat.com>,
	Andreas Schwab <schwab@suse.de>
Subject: Re: Is it OK to write ASCII strings directly into locale source files?
Date: Mon, 24 Jul 2017 22:51:00 -0000	[thread overview]
Message-ID: <364005592.108952.1500935986620@poczta.nazwa.pl> (raw)
In-Reply-To: <87379lczdi.fsf@mid.deneb.enyo.de>

24.07.2017 23:13 Florian Weimer <fw@deneb.enyo.de> wrote:
>
>
> * Carlos O'Donell:
>
> [...]
> > My only technical objection with writing straight UTF-8 is that it could
> > lead to more mistakes, and Mike just found one in CLDR where an Arabic
> > Farsi character was used incorrectly because it displayed the same glyph.
> > It was caught when harmonizing with glibc where you have to write out the
> > code points (Mike filed a bug upstream with CLDR).
>
> Wasn't it caught by locale testing which revealed that the locale
> wasn't compatible with ISO-8859-6? [...]

This is exactly what happened.  The character was not representable in
ISO-8859-6.  There was no problem in UTF-8.

> [...]
> > My preference would be to start small, start using the POSIX portable
> > character set to it's maximum extent for all latin-based languages,
>
> I would still prefer the <U…> encoding for control characters which
> are in the portable character set. So I have to object to the
> “maximum” part. :)

I agree modulo the concerns which I expressed in another email:
let's investigate the history behind it and if we still don't
know then let's just wait for the 2.26 release.

Regards,

Rafal

  reply	other threads:[~2017-07-24 22:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 13:13 Mike FABIAN
2017-07-24 13:28 ` Carlos O'Donell
2017-07-24 13:32   ` Mike FABIAN
2017-07-24 14:47     ` Carlos O'Donell
2017-07-24 15:03       ` Mike FABIAN
2017-07-24 15:45         ` Carlos O'Donell
2017-07-24 22:39       ` Rafal Luzynski
2017-07-24 22:55         ` Carlos O'Donell
2017-07-24 14:49   ` Andreas Schwab
2017-07-24 15:07     ` Carlos O'Donell
2017-07-24 17:07     ` Florian Weimer
2017-07-24 20:07       ` Carlos O'Donell
2017-07-24 22:34         ` Florian Weimer
2017-07-24 22:51           ` Rafal Luzynski [this message]
2017-07-25  5:40           ` Carlos O'Donell
2017-07-25  6:27             ` Mike FABIAN
2017-07-25 12:48               ` Carlos O'Donell
2017-07-25 14:21                 ` Florian Weimer
2017-07-25 14:37                   ` Carlos O'Donell
2017-07-25 19:05                     ` Florian Weimer

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=364005592.108952.1500935986620@poczta.nazwa.pl \
    --to=digitalfreak@lingonborough.com \
    --cc=carlos@redhat.com \
    --cc=fw@deneb.enyo.de \
    --cc=libc-alpha@sourceware.org \
    --cc=mfabian@redhat.com \
    --cc=schwab@suse.de \
    /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).