From: Florian Weimer <fw@deneb.enyo.de>
To: Andreas Schwab <schwab@suse.de>
Cc: Carlos O'Donell <carlos@redhat.com>,
Mike FABIAN <mfabian@redhat.com>,
libc-alpha@sourceware.org
Subject: Re: Is it OK to write ASCII strings directly into locale source files?
Date: Mon, 24 Jul 2017 17:07:00 -0000 [thread overview]
Message-ID: <87h8y13gvb.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <mvmy3rdx577.fsf@suse.de> (Andreas Schwab's message of "Mon, 24 Jul 2017 16:47:08 +0200")
* Andreas Schwab:
> On Jul 24 2017, Carlos O'Donell <carlos@redhat.com> wrote:
>
>> So let us start slowly and agree with 'ASCII - [<>]' where < denotes
>> the start of a code point and > the end of the code point.
>
> POSIX says "character in the portable character set" if you want to keep
> it portable.
But our locales only have to be compatible with our localedef, right?
I know that the FSF does not claim copyright on our locales, so anyone
is free to take them and use them with their own non-GNU systems (or
sell them as PDFs/books). But this does not mean we have to make
their lives easier if it comes at a cost to us (e.g., verifying that
we only use the portable character set, or refraining from using full
UTF-8 at a future date).
next prev parent reply other threads:[~2017-07-24 17:05 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 [this message]
2017-07-24 20:07 ` Carlos O'Donell
2017-07-24 22:34 ` Florian Weimer
2017-07-24 22:51 ` Rafal Luzynski
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=87h8y13gvb.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=carlos@redhat.com \
--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).