From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79204 invoked by alias); 29 Mar 2016 23:31:58 -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 79190 invoked by uid 89); 29 Mar 2016 23:31:57 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=levin, dmitry, Dmitry, H*M:4eec X-HELO: aev204.rev.netart.pl Date: Tue, 29 Mar 2016 23:31:00 -0000 From: Rafal Luzynski Reply-To: Rafal Luzynski To: "Dmitry V. Levin" Cc: libc-alpha@sourceware.org Message-ID: <666336576.426212.9ea90152-1d54-4eec-8ffa-81bfd328d92b.open-xchange@poczta.nazwa.pl> In-Reply-To: <20160329143132.GA28928@altlinux.org> References: <1155243857.420233.60a90901-4334-4cea-aa99-f76884316a10.open-xchange@poczta.nazwa.pl> <20160329143132.GA28928@altlinux.org> Subject: Re: [RFC][PATCH v2 3/6] Implement the %OB specifier - alternative month names (bug 10871) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Originating-Client: com.openexchange.ox.gui.dhtml X-SW-Source: 2016-03/txt/msg00717.txt.bz2 29.03.2016 16:31 "Dmitry V. Levin" wrote: > > > On Fri, Mar 25, 2016 at 01:55:13AM +0100, Rafal Luzynski wrote: > [...] > > This means that all applications using %B to retrieve the month > > name standalone should use %OB from now. > > Such applications as cal(1) would not be able to print month names > properly in a way that would work with different glibc versions. > Looks like this is a change incompatible in both ways. Yes, that's exactly what will happen. Such applications must be updated. They must start using strftime("%OB") and nl_langinfo(ALTMON_...). They must either detect the glibc version at runtime and choose the correct format specifier or require the minimum glibc version at build time. I'm willing to contact the upstream developers and provide the instructions how to change their applications. I encourage you to review and apply this fix early because other projects may need to adopt to this change. And, last but not least, thank you for mentioning cal(1), this is another application which probably will need to be updated. Best regards, Rafal