On Fri, Feb 23, 2018 at 9:15 PM, Alvaro Herrera
wrote:
> Clearly, for a few languages the current facilities are sufficient.
> If we make the process easier, we're likely to have more translations.
> Will there be people verifying the quality also?
It seems to me that making the process easier ha
Tels wrote:
> Last but not least I'd be able to help with the german translation, but I
> have no clear idea how, or what the actual status is. Are German
> translators actually needed?
German, along with Russian and French, are pretty much the only
translations kept fully up to date almost all t
On Fri, Feb 23, 2018 at 2:09 PM, Peter Eisentraut
wrote:
> 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.
Good to k
On 2/23/18 10:48, Robert Haas wrote:
> On Fri, Feb 23, 2018 at 10:41 AM, Tom Lane wrote:
>> Thom Brown 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 s
On Thu, February 22, 2018 11:04 pm, Tom Lane wrote:
> Alvaro Herrera writes:
>> Please join pgsql-translat...@postgresql.org.
>
> What surprises me about this thread is that apparently the sad state
> of the v10 translations wasn't already discussed on that list?
The list is more or less dead -
On Fri, Feb 23, 2018 at 10:41 AM, Tom Lane wrote:
> Thom Brown 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
Thom Brown 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
On 23 February 2018 at 04:04, Tom Lane wrote:
> Alvaro Herrera writes:
>> Please join pgsql-translat...@postgresql.org.
>
> What surprises me about this thread is that apparently the sad state
> of the v10 translations wasn't already discussed on that list?
>
> I have no objection to calling for
Alvaro Herrera writes:
> Please join pgsql-translat...@postgresql.org.
What surprises me about this thread is that apparently the sad state
of the v10 translations wasn't already discussed on that list?
I have no objection to calling for more translation volunteers on
this list --- in fact, prob
On 23 February 2018 at 09:50, Tatsuo Ishii wrote:
> > I was wondering a bit about how translations are maintained. Experience
> > with another highly internationalised project years ago showed that many
> > people who are willing to volunteer as translators are NOT willing to
> > interact with gi
> On Fri, Feb 23, 2018 at 09:51:02AM +0900, Tatsuo Ishii wrote:
>> I'm not working on message translations. Hotta-san is actively
>> working on the translations here:
>>
>> https://github.com/hotta/pg-nls-ja
>
> If you need help here, feel free to ping me. I have done translation to
> Japanese
> Michael Paquier wrote:
>> On Fri, Feb 23, 2018 at 09:51:02AM +0900, Tatsuo Ishii wrote:
>> > I'm not working on message translations. Hotta-san is actively
>> > working on the translations here:
>> >
>> > https://github.com/hotta/pg-nls-ja
>>
>> If you need help here, feel free to ping me. I
On Thu, Feb 22, 2018 at 11:45:11PM -0300, Alvaro Herrera wrote:
> How many repositories do we need, though? There is already one in
> git.postgresql.org -- see https://babel.postgresql.org/
Centralizing things into postgresql.org is nice for the long term.
> Please join pgsql-translat...@postgre
Michael Paquier wrote:
> On Fri, Feb 23, 2018 at 09:51:02AM +0900, Tatsuo Ishii wrote:
> > I'm not working on message translations. Hotta-san is actively
> > working on the translations here:
> >
> > https://github.com/hotta/pg-nls-ja
>
> If you need help here, feel free to ping me. I have done
On Fri, Feb 23, 2018 at 09:51:02AM +0900, Tatsuo Ishii wrote:
> I'm not working on message translations. Hotta-san is actively
> working on the translations here:
>
> https://github.com/hotta/pg-nls-ja
If you need help here, feel free to ping me. I have done translation to
Japanese for other th
> I was wondering a bit about how translations are maintained. Experience
> with another highly internationalised project years ago showed that many
> people who are willing to volunteer as translators are NOT willing to
> interact with git (or at the time, svn) and the other tools many of us take
On 23 February 2018 at 08:51, Tatsuo Ishii wrote:
> > I also noticed the same thing few days ago, by the fact that RPM
> > release of PG10 doesn't contain psql translation.
> >
> > @10 > ja | pg_basebackup,pg_resetxlog,
> plpython,pltcl,postgres,psql
> > @9.4> ja | pg_basebackup,pg_
> I also noticed the same thing few days ago, by the fact that RPM
> release of PG10 doesn't contain psql translation.
>
> @10 > ja | pg_basebackup,pg_resetxlog,plpython,pltcl,postgres,psql
> @9.4> ja | pg_basebackup,pg_resetxlog
>
> I'm not sure how the translations are maintained
# my clone repository has been corrupted...sigh.
At Thu, 22 Feb 2018 18:32:15 -0500, Robert Haas wrote
in
> On Thu, Feb 22, 2018 at 5:54 PM, Tatsuo Ishii wrote:
> >> I have found that Japanese language support for the database server
> >> has been dropped for 10. This is because it fell below
>> Was that mentioned in the 10.0 release note? I didn't know that.
>
> I don't think we ever mention translations that are added or dropped
> in minor release notes.
I think it would better for users to be noticed that in the release
notes because the message translations are apparently visible
On Thu, Feb 22, 2018 at 5:54 PM, Tatsuo Ishii wrote:
>> 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.
>
> Was that mentioned in the 10.
> 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.
Was that mentioned in the 10.0 release note? I didn't know that.
Best regards,
--
Tatsuo
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 +, Thom Brown wrote:
On 22 February 2018 at 17:24, Magnus Hagander wrote:
> On Thu, Feb 22, 2018 at 6:20 PM, Thom Brown 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
On Thu, Feb 22, 2018 at 6:20 PM, Thom Brown 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 comp
2018-02-22 18:20 GMT+01:00 Thom Brown :
> 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
26 matches
Mail list logo
