From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 86417 invoked by alias); 24 Jul 2017 17:05:44 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 85714 invoked by uid 89); 24 Jul 2017 17:05:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*r:TLS1.2, pdfs, PDFs, books X-HELO: albireo.enyo.de From: Florian Weimer To: Andreas Schwab Cc: Carlos O'Donell , Mike FABIAN , libc-alpha@sourceware.org Subject: Re: Is it OK to write ASCII strings directly into locale source files? References: <5f71f2f6-be0e-2b5d-91ce-03386eafa7f7@redhat.com> Date: Mon, 24 Jul 2017 17:07:00 -0000 In-Reply-To: (Andreas Schwab's message of "Mon, 24 Jul 2017 16:47:08 +0200") Message-ID: <87h8y13gvb.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2017-07/txt/msg00820.txt.bz2 * Andreas Schwab: > On Jul 24 2017, Carlos O'Donell 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).