Re: Translations contributions urgently needed

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thom Brown <thom(at)linux(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Translations contributions urgently needed
Date: 2018-02-23 15:48:35
Message-ID: CA+TgmoY6PORb0OFDkH=JCep3iqSehgAuTTcaNaQZR00taJ6jSw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 23, 2018 at 10:41 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thom Brown <thom(at)linux(dot)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".

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-02-23 16:05:23 Re: RTLD_GLOBAL (& JIT inlining)
Previous Message Tom Lane 2018-02-23 15:41:38 Re: Translations contributions urgently needed