This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Is it OK to write ASCII strings directly into locale source files?
On 07/24/2017 10:49 AM, Mike FABIAN wrote:
> Carlos O'Donell <carlos@redhat.com> さんはかきました:
>
>> On 07/24/2017 09:28 AM, Mike FABIAN wrote:
>>> Carlos O'Donell <carlos@redhat.com> wrote:
>>>
>>>> On 07/24/2017 09:09 AM, Mike FABIAN wrote:
>
> [...]
>
>>> Yes, that sounds like a very reasonable first step!
>>>
>>> Is it OK to use that already *now*?
>>
>> You and Rafal are localedata maintainers, you can assume consensus, therefore
>> you can start changing things in whatever way you wish.
>>
>> Before you change this though I would like to see your list of reasons
>> for making the change, what benefits do you see it bringing? Is readability
>> the only one?
>
> Readability is the only reason for me at the moment, editing these files
> using the code points is very tedious and error prone.
Sounds like a good reason to me.
>>> So maybe it is possible to use that right now without having to change
>>> anything in the code parsing the locale source files.
>>
>> You need to document somewhere what is acceptable and what is not and
>> which ASCII characters cannot be used.
>
> Where should that be documented?
Andreas Schwab just pointed out that we should already technically support
using any character in the POSIX portable character set in the locale definitions.
So I think there is nothing to comment, and we are still within the definition of
POSIX for making these locales portable.
So feel free to change any UTF-8 code points into their equivalent POSIX portable
character set characters.
--
Cheers,
Carlos.