From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9860 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Re: [bug-gettext] AM_GNU_GETTEXT without referring internal symbols? Date: Thu, 7 Apr 2016 09:53:36 -0400 Message-ID: <20160407135336.GN21636@brightrain.aerifal.cx> References: <20160407062659.GM21636@brightrain.aerifal.cx> <20160407105746.GF9862@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1460037236 16836 80.91.229.3 (7 Apr 2016 13:53:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 7 Apr 2016 13:53:56 +0000 (UTC) To: Masanori Ogino , musl@lists.openwall.com, bug-gnu-gettext@gnu.org Original-X-From: musl-return-9873-gllmg-musl=m.gmane.org@lists.openwall.com Thu Apr 07 15:53:56 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1aoANe-0007Q2-Nb for gllmg-musl@m.gmane.org; Thu, 07 Apr 2016 15:53:54 +0200 Original-Received: (qmail 21591 invoked by uid 550); 7 Apr 2016 13:53:51 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 21567 invoked from network); 7 Apr 2016 13:53:50 -0000 Content-Disposition: inline In-Reply-To: <20160407105746.GF9862@port70.net> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:9860 Archived-At: On Thu, Apr 07, 2016 at 12:57:47PM +0200, Szabolcs Nagy wrote: > * Masanori Ogino [2016-04-07 16:12:39 +0900]: > > 2016-04-07 15:26 GMT+09:00 Rich Felker : > > > I'm not sure what the %Id thing you're referring to is; can you point > > > me to a description of it? > > > > %Id is essentially an extension of printf(3) in glibc 2.2 and later. > > It can be implemented by the same way as how sysdep is implemented; it > > just depends on the current locale, not the ABI. > > > > Search http://man7.org/linux/man-pages/man3/sprintf.3.html by "glibc > > 2.2 adds" for details. > > i think it is not acceptable that glibc introduces > extensions that can collide with future versions of > the c and posix standards. > > but it is even worse if a translation file format > depends on such extensions which makes it hard to > fix the problem once the collision happens > (like it happened with scanf %a). > > there are other problems with this flag, so gettext > manual should recommend some other solution. In that case this has nothing to do with gettext capabilities; gettext does not process format strings but simply translates one format strign to another, and if a program is using non-portable format strings, it's going to break whether it's using gettext or not. So I don't think it's relevant to this discussion of whether _gettext_ is compatible. Rich