From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-82372-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 87123 invoked by alias); 24 Jul 2017 15:03:13 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 87100 invoked by uid 89); 24 Jul 2017 15:03:11 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=no version=3.3.2 spammy=reserved
X-HELO: mail-qk0-f180.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:subject:to:cc:references:from:organization
         :message-id:date:user-agent:mime-version:in-reply-to
         :content-language:content-transfer-encoding;
        bh=qUauKPdwuzxeOx9f5Uv4vpH9HCIwRBUhQjIk1YdtQXc=;
        b=lSVZI35cO3/Ab7FyxNfLOfcX2eXcQSRlADbz9zC6WEB7eOfCZVWa6/QVmmC8j6R1mG
         tS/N4Yym1OBJv+CDn5qulL/PiWWM6ounNmgWWj00wXk40siPdDrRhQUuXseqIHGZHmmf
         IDMemy230/l5U1V1qYxyngEW2LZKbz9oOKjZLSTdQy3OqgrRx3hdbiuxq2vBXI8BdoHP
         DgNLYK51W8YQ/btjLGTPZI5fvSOwR/xk8P60EC/VTy9V0SWlnaJo0n3Dy4U9YzKfd4QJ
         mMs8/BIx25Ft0gYNNhQeAQSpzyHbtQv4+pz4k46gVkgFrLKQLqMew2JPGbfAh/L3PlnQ
         6dWA==
X-Gm-Message-State: AIVw110SoG44b+B8ZMGkiulMzvvaL/vJa03wbG2SqqoNC3/QG1GyY3By
	tYhkr1yIGAvFDzER/XNXPw==
X-Received: by 10.55.5.131 with SMTP id 125mr21344329qkf.28.1500908588067;
        Mon, 24 Jul 2017 08:03:08 -0700 (PDT)
Subject: Re: Is it OK to write ASCII strings directly into locale source
 files?
To: Andreas Schwab <schwab@suse.de>
Cc: Mike FABIAN <mfabian@redhat.com>, libc-alpha@sourceware.org
References: <s9d8tje9e1k.fsf@redhat.com>
 <5f71f2f6-be0e-2b5d-91ce-03386eafa7f7@redhat.com> <mvmy3rdx577.fsf@suse.de>
From: Carlos O'Donell <carlos@redhat.com>
Message-ID: <68f8c74c-8fa3-ad89-2e00-e194b29a4794@redhat.com>
Date: Mon, 24 Jul 2017 15:07:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <mvmy3rdx577.fsf@suse.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-SW-Source: 2017-07/txt/msg00816.txt.bz2

On 07/24/2017 10:47 AM, Andreas Schwab wrote:
> 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.

Yes, that's right, and the "7.3 Locale Definition" already says that "<"
is in the reserved namespace and must be escaped to be used literally.

So we should already support using characters from the POSIX portable
character set with proper escaping.

-- 
Cheers,
Carlos.