From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 99025 invoked by alias); 7 Jun 2019 00:58:02 -0000 Mailing-List: contact libc-locales-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-locales-owner@sourceware.org Received: (qmail 99005 invoked by uid 89); 7 Jun 2019 00:58:01 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_00,BODY_8BITS,GARBLED_BODY,KAM_MANYTO,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1 spammy=H*f:@kobylkin.com, H*f:sk:DDiRMB9, H*f:sk:2030695, HTo:U*siddhesh X-HELO: mail-qk1-f176.google.com Return-Path: Subject: Re: [PING^8][PATCH v12] Locales: Cyrillic -> ASCII transliteration [BZ #2872] To: Rafal Luzynski , Marko Myllynen , "Diego (Egor) Kobylkin" , "libc-alpha@sourceware.org" , "libc-locales@sourceware.org" , Siddhesh Poyarekar Cc: Mike Fabian References: <2030695416.914859.1559778544120@poczta.nazwa.pl> <1640311749.1550210.1559856673283@poczta.nazwa.pl> From: Carlos O'Donell Message-ID: <054f3b06-3ca8-00b0-ee07-1ff86a4106dc@redhat.com> Date: Fri, 07 Jun 2019 00:58:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <1640311749.1550210.1559856673283@poczta.nazwa.pl> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2019-q2/txt/msg00081.txt.bz2 On 6/6/19 5:31 PM, Rafal Luzynski wrote: >>> Possible answers (Cyrillic -> Latin Extended -> ASCII): >>> >>> 1. "Ш" -> "Š" -> "SH" >>> >>> e.g.: "Шема" -> "Šema" -> "SHema" >>> "Схема" ----------> "Shema" >>> >>> 2. "Ш" -> "Š" -> "Sh" >>> >>> e.g.: "Шема" -> "Šema" -> "Shema" >>> "Схема" ----------> "Shema" >>> >>> Personally I don't like the answer 1. because "SHema" looks weird >>> to me. Egor in turn does not like the answer 2. because the output >>> string becomes ambiguous. >>> >>> Should we maybe have a smart algorithm which would select the title >>> case or the upper case of the output characters depending on the >>> context in the word? Note that it would not resolve the problem of >>> the output text being ambiguous. >> >> It seems clear that there is no one right/wrong answer but it's a matter >> of preference, especially the way this currently works. It might be an >> improvement to output (for instance) SH instead of Sh if all the other >> letters of a word are upper-case as well but not sure what would help >> with the result being unambiguous. > > I think you refer to the idea of implementing a smart algorithm which would > adapt the lower/upper case depending on the context but indeed it would > not resolve the problem of ambiguity. > > So, the smart algorithm aside, what should be the preferred transliteration > rule? I have a weak preference for 1. However, I would change my preference if someone showed me existing prior implementations that did 1 or 2. -- Cheers, Carlos.