Re: Translations contributions urgently needed
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thom Brown <thom@linux.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>,
Michael Paquier <michael@paquier.xyz>, Tatsuo Ishii <ishii@sraoss.co.jp>,
Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-02-23T19:09:42Z
Lists: pgsql-hackers
On 2/23/18 10:48, Robert Haas wrote: > On Fri, Feb 23, 2018 at 10:41 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Thom Brown <thom@linux.com> writes: >>> Something that isn't clear to me is, for a language that didn't meet >>> 80% translation for a component, if it does reach 80% after the major >>> version release, does it then get shipped in a minor release, or is >>> out of that version completely until the next major version? >> >> No, it'll be added to the next minor release as soon as it reaches >> 80%. That's happened routinely in the past. I have no idea how >> automated that policy is -- you could ask Peter E. -- but a trawl >> through the commit logs shows .po files getting added in minor >> releases from time to time. > > https://wiki.postgresql.org/wiki/NLS#Minimum_Translation implies the > opposite, because it refers to inclusion "in a PostgreSQL major > release". That section is meant to say, if a translation ships in 10.0 with 81% but then drops to 79% because some backpatching changes strings, we won't drop it in 10.2. In the opposite case, it would be added to a minor release. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services