From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36577 invoked by alias); 24 May 2017 23:25:28 -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 36559 invoked by uid 89); 24 May 2017 23:25:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=vaguely, hearing, H*Ad:D*ucla.edu X-HELO: zimbra.cs.ucla.edu Subject: Re: Locale with shift state To: libc-alpha@sourceware.org References: <842477bc-1e08-278b-2361-7d0884100fef@redhat.com> From: Paul Eggert Message-ID: <2a1ec7ca-d256-983c-0b24-dc638d02396a@cs.ucla.edu> Date: Wed, 24 May 2017 23:25:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <842477bc-1e08-278b-2361-7d0884100fef@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2017-05/txt/msg00745.txt.bz2 On 05/24/2017 08:27 AM, Florian Weimer wrote: > Do we have a locale with a multi-byte character set which has shift > state (beyond a truncated multi-byte conversion)? We support such > charsets in iconv, but I can't find a locale which uses them. I doubt whether we have any such locales. > Would such a locale even be POSIX-compatible? It depends what you mean by "POSIX-compatible". Locking-shift encodings cannot be defined by POSIX-compatible character set description files, and POSIX does not require support for such encodings. See: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap06.html#tag_06_04 Although a POSIX implementation could provide extensions to the character set description format and/or a builtin locale that supports such locking-shift encodings, I don't know of any practical POSIX implementation that does so. I vaguely recall hearing of attempts to build such systems many years ago for ISO-2022-JP, and that they didn't work.