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

From Ioseph Kim
Subject Re: Translations contributions urgently needed
Date
Msg-id 20180222174712.ab6l3eqwvrno6x34@postgresql.kr
Whole thread Raw
In response to Re: Translations contributions urgently needed  (Thom Brown <thom@linux.com>)
List pgsql-hackers
Hi, I’m translating to Korean since 10 years over.
I think this issue should be left to the local community.
It may be omitted in some versions, or added in some versions.
because, it depends on volunteering.
Let It Be!

Regards Ioseph.


On Thu, Feb 22, 2018 at 05:29:11PM +0000, Thom Brown wrote:
> On 22 February 2018 at 17:24, Magnus Hagander <magnus@hagander.net> wrote:
> > 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?
> 
> Oh yes, okay, that's true.  I guess we can ignore those, so it's a
> little less dire for 9.6 to 10 then.  We get this instead, which is
> still not good:
> 
>  cs       | plpython
>  id       | postgres
>  it       | pg_resetxlog
>  ja       | pg_basebackup,plpython,pltcl,postgres,psql
>  pt_BR    | pg_basebackup,pltcl,postgres
>  tr       | plperl
>  zh_CN    | pg_basebackup,pltcl
>  zh_TW    | plperl
> 
> Thom
> 


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Online enabling of checksums
Next
From: Magnus Hagander
Date:
Subject: Allow workers to override datallowconn