From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
cc: ertugrul9090@gmail.com,
        Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15511: Drop table error "invalid argument"
In-reply-to: <20181206192422.nlxxj37hoi4p4b6o@alvherre.pgsql>
References: <20181206192422.nlxxj37hoi4p4b6o@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@2ndquadrant.com>
	message dated "Thu, 06 Dec 2018 16:24:22 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <21375.1544125630.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Thu, 06 Dec 2018 14:47:10 -0500
Message-ID: <21376.1544125630@sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2018-Nov-17, Tom Lane wrote:
>> I poked at that to the extent of testing every string in 11.1's tr.po
>> against our implementation of snprintf, and what I find is this:
>> msgid "column %s of %s"
>> msgstr "%2$s'nin %1$ sütunu"

> I fixed this string in tr.po.  At least it'll be correct in 11.2.

Thanks!  I'm also just about to push code changes for the easy parts
of what I recommended earlier (have psprintf report the bogus format
string, and make snprintf.c throw EINVAL for more error cases).

Is anybody interested in the idea of making our own validator for
the .po files?  I might be willing to code it up, if I knew what
its API ought to be, but I don't know the workflow in that area.

			regards, tom lane