From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 38447 invoked by alias); 9 Nov 2016 11:00:40 -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 38433 invoked by uid 89); 9 Nov 2016 11:00:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.8 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=phrases, romance, expressed, month X-HELO: mx1.redhat.com Subject: Re: [RFC][PATCH v4 06/11] Provide backward compatibility for strftime family (bug 10871). To: Rafal Luzynski References: <758885038.1799972.1477615768169@poczta.nazwa.pl> <71b7640e-55b0-06a5-1dff-b0fcbaf0eea9@redhat.com> <1458120697.2205845.1478343189427@poczta.nazwa.pl> <238ab162-7ff7-d90e-9f95-630ac413a064@redhat.com> Cc: libc-alpha@sourceware.org From: Florian Weimer Message-ID: <30c831e4-8825-75e4-c81e-7e260054efb1@redhat.com> Date: Wed, 09 Nov 2016 11:00:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <238ab162-7ff7-d90e-9f95-630ac413a064@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2016-11/txt/msg00322.txt.bz2 On 11/07/2016 03:13 PM, Florian Weimer wrote: > One example where this matters is German. If POSIX requires that %B > returns the genitive case, as has been suggested, then all applications > which currently use %B are broken because I have yet to see a > mechanically generated German date string which actually needs the > genitive case. In current usage, they only occur in phrases such “on > the last Sunday of November”. The concern expressed in the paragraph above is not relevant because it's about month name mangling for inclusion in full date strings, and not about declension. German does not have an issue with that, but many Romance languages do because some of them do require such mangling in full date strings, as explained here: https://sourceware.org/ml/libc-alpha/2016-11/msg00321.html To be absolutely clear, I still object to the change to %B (and MON_1 etc.) and moving the old definitions to %OB (ALTMON_1 etc.). The right way to do this is to leave %B (MON_1 etc.) alone and add %OB (ALTMON_1 etc.) with the new mangled form. This also removes the surprising change of behavior due to a simple recompilation of unchanged sources. As there has been some confusion regarding past objections of mine which were apparently worded in too a conciliatory way, I consider this a sustained objection under the glibc consensus protocol. Thanks, Florian