From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28659 invoked by alias); 4 Feb 2019 07:14:29 -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 28639 invoked by uid 89); 4 Feb 2019 07:14:29 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=Country, alternatives, learned, comfortable X-HELO: mout.kundenserver.de Subject: Re: [PATCH v12] Locales: Cyrillic -> ASCII transliteration [BZ #2872] ping for 2.30 To: libc-alpha@sourceware.org, libc-locales@sourceware.org, Carlos O'Donell Cc: Marko Myllynen , Rafal Luzynski , Siddhesh Poyarekar , 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: Egor Kobylkin Message-ID: <41aff10b-9cf1-638c-4fbc-8c4f4122f2e9@kobylkin.com> Date: Mon, 04 Feb 2019 07:14:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2019-q1/txt/msg00035.txt.bz2 Carlos, are you comfortable to pick this up again this month? I would really love to have a reliable action plan to get this committed for 2.30. Maybe cut out a subset that is undisputed and commit only that first. It looks kinda like an eternal moving target otherwise. for you reference: https://sourceware.org/ml/libc-alpha/2019-01/msg00036.html https://sourceware.org/ml/libc-alpha/2019-01/msg00040.html Bests, Egor Kobylkin On 09.01.19 21:03, Marko Myllynen wrote: > 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, >