Re: Translations contributions urgently needed - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Translations contributions urgently needed
Date
Msg-id CABUevEzzYPG2D2X+1NtNLA7MsRtM1UgbrhSz3UzkZNOjY4Gfhw@mail.gmail.com
Whole thread Raw
In response to Translations contributions urgently needed  (Thom Brown <thom@linux.com>)
Responses Re: Translations contributions urgently needed
List pgsql-hackers
On Thu, Feb 22, 2018 at 6:20 PM, Thom Brown <thom@linux.com> wrote:
Hi,

I have found that Japanese language support for the database server
has been dropped for 10.  This is because it fell below the 80% of
strings translated requirement, so it was shipped without Japanese.
This isn't true of all components, but it seems quite alarming that
we've pushed out PostgreSQL 10 with no language support for a country
that has contributed a significant amount to the project, and has a
relatively large number of users.

The database server also dropped support for Indonesian and Portugese
(Brazil).  In fact, just between 9.6 and 10, the following language
support was dropped for these components:

 cs       | plpython
 de       | pg_resetxlog
 es       | pg_resetxlog
 fr       | pg_resetxlog
 id       | postgres
 it       | pg_resetxlog
 ja       | pg_basebackup,pg_resetxlog,plpython,pltcl,postgres,psql
 ko       | pg_resetxlog
 pl       | pg_resetxlog
 pt_BR    | pg_basebackup,pg_resetxlog,pltcl,postgres
 ru       | pg_resetxlog
 sv       | pg_resetxlog
 tr       | plperl
 zh_CN    | pg_basebackup,pg_resetxlog,pltcl
 zh_TW    | plperl

Arent all those pg_resetxlog entries because it was renamed to pg_resetwal? Is that because they were actually not updated for the new name, or is it a reporting side effect?

-- 

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Translations contributions urgently needed
Next
From: Nikolay Shaplov
Date:
Subject: Re: [HACKERS] [PATCH] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind for custom AM