From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 1623F1F803 for ; Wed, 9 Jan 2019 20:03:27 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:to:cc:references:from :message-id:date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=n0298RtyVl/B/9ul oJHV4Z1NCcTyDpjPFfhYBYwhrCH9uUWQdKVTqOCeaiOpBElqgb6Ko5AytQuzzpop MG2O+5oHni1LKUh9mKWAhuuIP+edK3Wxsmo5aQrwKyy2qz/rHJo1uFXdDmzaREfQ wzmjfYRa1bJYOjGWNVt1wdl1t/o= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:to:cc:references:from :message-id:date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=9VL/J2XEHCKGwLe3XNdSvo U62XA=; b=wr8c/pa+sBe6LoXexyXZdeBH4vwX4BFVU7J7sDiF5fC4eP/lO953PL xgOM+8dzGzSru1sMzSZorpSp2JvUTEj/Rf0xpkHquUgZqzkredOionNW+xZtDZ2q HcunSYC4NlQNqZDBnvAmU6v/wLVQFktCqRx2YRUz4xuXTTiI45A/I= Received: (qmail 81846 invoked by alias); 9 Jan 2019 20:03:21 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 81495 invoked by uid 89); 9 Jan 2019 20:03:20 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mail-wr1-f65.google.com Reply-To: Marko Myllynen Subject: Re: [PATCH v12] Locales: Cyrillic -> ASCII transliteration [BZ #2872] To: Egor Kobylkin , Rafal Luzynski , libc-alpha@sourceware.org, libc-locales@sourceware.org, Carlos O'Donell , Siddhesh Poyarekar Cc: Mike Fabian References: <41532e13-a63d-5df1-ab37-05eb4d6c8d0a@kobylkin.com> <20180412224352.GB2911@altlinux.org> <2124833400.35614.1546698902753@poczta.nazwa.pl> <908ed415-cfe4-804c-f421-4351ef062edc@kobylkin.com> <6d076299-babd-406a-b1fe-87778f54bf36@kobylkin.com> From: Marko Myllynen Message-ID: Date: Wed, 9 Jan 2019 22:03:09 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: <6d076299-babd-406a-b1fe-87778f54bf36@kobylkin.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, On 09/01/2019 02.46, Egor Kobylkin wrote: > On 07.01.19 21:37, Marko Myllynen wrote: >> On 05/01/2019 23.12, Egor Kobylkin wrote: >>> >>> Good catch! Should we maybe split this into two patches, one for C and >>> the other for "country" locales? They have different codes and >>> functionality so it looks like it would be easier to keep focus. >> >> That would probably make sense, the standard C/POSIX locale won't >> support System A so it also narrows down solution alternatives with it. >> >>> "Country" locales in localedata/locales/ can then have the exact same >>> translit table included or they can have any other flavor - I don't see >>> a problem here. >> >> Indeed, and since those files are not limited to ASCII, perhaps we could >> now reconsider the v9 approach for them, i.e., prefer System A if >> possible, otherwise use System B / ASCII (just need to make sure that >> the ASCII fall-back for them will match the built-in C ASCII rule)? > > Happy to hear the split seems to be a clear cut one. > How about I rename the "[PATCH v12]...[BZ #2872]" to "[PATCH v1]... > C/POSIX [BZ #2872]" and the "[PATCH v9]" gets its own bug-report > (number) and title for clarity in communication? I'm not sure is a new BZ really needed for such an addition, perhaps a NEWS entry might be more appropriate (with the full details explained in the commit messages of course) but I'll leave this to others to decide. > This way it would probably be easier to have the decision making process > tied up for both patches (separately). We may want to get the v12 POSIX > out of the door in 2.30 then and can take all the time we need to set up > the rules for "Countries" locales as you need them to be. Perhaps Rafal or Carlos have better suggestions but I would think we could have a patch series where the patch 1/3 adds the C/POSIX locale part (that would be what you posted as v12), then patch 2/3 adds translit_cyrillic (based on your v9 so supports ISO 9.1995 / GOST 7.79 System A and GOST 7.79 System B as a fall-back (which would match the C/POSIX rules)), and finally the patch 3/3 updates locales to use translit_cyrillic as appropriate. But as said, Rafal or Carlos may have alternative suggestions so it might be best to wait for their feedback before doing anything yet (it's unfortunate you've had to do so many iterations around this already but I think we've all learned something during the process and the end result will be more correct than any of the earlier versions). Thanks, -- Marko Myllynen