Fix japanese translation of log messages

At Fri, 26 Aug 2022 10:23:01 +0900, Shinya Kato <Shinya11.Kato@oss.nttdata.com> wrote in

I've found typos in ja.po, and fixed them.
The patch is attached.

(This is not for -hackers but I'm fine with it being posted here;p)

Thanks for the report! Pushed to 10 to 15 of translation repository
with some minor changes. They will be reflected in the code tree some
time later.

msgid "More details may be available in the server log."
-msgstr "詳細な情報がはサーバログにあるかもしれません。"
+msgstr "詳細な情報はサーバログにあるかもしれません。"

I prefer "詳細な情報が" than "詳細な情報は" here. (The existnce of
the details is unknown here.)

 msgid "cannot drop active portal \"%s\""
-msgstr "アクテイブなポータル\"%s\"を削除できません"
+msgstr "アクティブなポータル\"%s\"を削除できません"

I canged it to "アクティブなポータル\"%s\"は削除できません". (It
describes state facts, not telling the result of an action.)

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

On 2022-08-26 10:23, Shinya Kato wrote:

Hi hackers,

I've found typos in ja.po, and fixed them.
The patch is attached.

Thanks for the patch!
LGTM.

I had found a similar typo before in ja.po, so I added that as well.

@@ -12739,7 +12739,7 @@ msgstr "ロールオプション\"%s\"が認識できません"

#: gram.y:1588 gram.y:1604
#, c-format
msgid "CREATE SCHEMA IF NOT EXISTS cannot include schema elements"
-msgstr "CREATE SCHEMA IF NOT EXISTSんはスキーマ要素を含めることはできません"
+msgstr "CREATE SCHEMA IF NOT EXISTSはスキーマ要素を含めることはできません"

How do you think?

--
Regards,

--
Atsushi Torikoshi
NTT DATA CORPORATION

At Fri, 26 Aug 2022 14:28:26 +0900, torikoshia <torikoshia@oss.nttdata.com> wrote in

"

#: gram.y:1588 gram.y:1604
#, c-format
msgid "CREATE SCHEMA IF NOT EXISTS cannot include schema elements"
-msgstr "CREATE SCHEMA IF NOT EXISTSんはスキーマ要素を含めることはでき
-ません"
+msgstr "CREATE SCHEMA IF NOT EXISTSはスキーマ要素を含めることはできま
せん"

How do you think?

"NHa" Darn... That kind of mistypes are inevitable when I worked on
nearly or over a thousand of messages at once.. Currently I'm working
in an incremental fashion and I only process at most up to 10 or so
messages at a time thus that kind of silly mistake cannot happen..

It's a mistake of "には". I'll load it into the next ship. The next
release is 9/8 and I'm not sure the limit of translation commits for
the release, though..

Anyway, thank you for reporting!

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

On 2022-08-26 15:20, Kyotaro Horiguchi wrote:

At Fri, 26 Aug 2022 14:28:26 +0900, torikoshia
<torikoshia@oss.nttdata.com> wrote in

#: gram.y:1588 gram.y:1604
#, c-format
msgid "CREATE SCHEMA IF NOT EXISTS cannot include schema elements"
-msgstr "CREATE SCHEMA IF NOT EXISTSんはスキーマ要素を含めることはでき
-ません"
+msgstr "CREATE SCHEMA IF NOT EXISTSはスキーマ要素を含めることはできま
せん"

How do you think?

"NHa" Darn... That kind of mistypes are inevitable when I worked on
nearly or over a thousand of messages at once.. Currently I'm working
in an incremental fashion and I only process at most up to 10 or so
messages at a time thus that kind of silly mistake cannot happen..

No problem, rather thanks for working on this!

It's a mistake of "には".

Ah, I got it.

I'll load it into the next ship. The next
release is 9/8 and I'm not sure the limit of translation commits for
the release, though..

Thanks a lot!

--
Regards,

--
Atsushi Torikoshi
NTT DATA CORPORATION

On 2022-08-26 14:07, Kyotaro Horiguchi wrote:

At Fri, 26 Aug 2022 10:23:01 +0900, Shinya Kato
<Shinya11.Kato@oss.nttdata.com> wrote in

I've found typos in ja.po, and fixed them.
The patch is attached.

(This is not for -hackers but I'm fine with it being posted here;p)

Sorry, I didn't know there was an pgsql-translators.

Thanks for the report! Pushed to 10 to 15 of translation repository
with some minor changes. They will be reflected in the code tree some
time later.

Thanks!

msgid "More details may be available in the server log."
-msgstr "詳細な情報がはサーバログにあるかもしれません。"
+msgstr "詳細な情報はサーバログにあるかもしれません。"

I prefer "詳細な情報が" than "詳細な情報は" here. (The existnce of
the details is unknown here.)

msgid "cannot drop active portal \"%s\""
-msgstr "アクテイブなポータル\"%s\"を削除できません"
+msgstr "アクティブなポータル\"%s\"を削除できません"

I canged it to "アクティブなポータル\"%s\"は削除できません". (It
describes state facts, not telling the result of an action.)

Thanks, LGTM.

--
Regards,

--
Shinya Kato
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

On 2022-Aug-26, Kyotaro Horiguchi wrote:

It's a mistake of "には". I'll load it into the next ship. The next
release is 9/8 and I'm not sure the limit of translation commits for
the release, though..

Typically the translations are updated from the pgtranslation repository
on Monday of the release week, at around noon European time. You can
keep translating till the previous Sunday if you feel like it :-)

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/

At Fri, 26 Aug 2022 10:25:17 +0200, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote in

Typically the translations are updated from the pgtranslation repository
on Monday of the release week, at around noon European time. You can
keep translating till the previous Sunday if you feel like it :-)

Yeah... . .

So.. the limit is around 9/5 12:00 CEST(?).. is.. 9/5 19:00 JST?

Thank you very much for the significant info.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

On 2022-Aug-26, Kyotaro Horiguchi wrote:

At Fri, 26 Aug 2022 10:25:17 +0200, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote in

Typically the translations are updated from the pgtranslation repository
on Monday of the release week, at around noon European time. You can
keep translating till the previous Sunday if you feel like it :-)

Yeah... . .

So.. the limit is around 9/5 12:00 CEST(?).. is.. 9/5 19:00 JST?

Well, Sept 8th is the date of 15 beta4. I suppose there'll be at least
two or three weeks from beta4 to the RC1, and maybe one or two more
weeks from there to 15.0. You can obviously continue to translate until
then, if you want these translations to appear in 15.0. And as for
stable branches, the next one is scheduled for early November, so you
have until then to fix typos in those.

For any translations that do not appear in 15.0, you have three more
months until 15.1 ... and so on.

It never ends. Blessing or curse?

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
Officer Krupke, what are we to do?
Gee, officer Krupke, Krup you! (West Side Story, "Gee, Officer Krupke")

At Fri, 26 Aug 2022 11:07:13 +0200, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote in

On 2022-Aug-26, Kyotaro Horiguchi wrote:

At Fri, 26 Aug 2022 10:25:17 +0200, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote in

Typically the translations are updated from the pgtranslation repository
on Monday of the release week, at around noon European time. You can
keep translating till the previous Sunday if you feel like it :-)

Yeah... . .

So.. the limit is around 9/5 12:00 CEST(?).. is.. 9/5 19:00 JST?

Well, Sept 8th is the date of 15 beta4. I suppose there'll be at least
two or three weeks from beta4 to the RC1, and maybe one or two more
weeks from there to 15.0. You can obviously continue to translate until
then, if you want these translations to appear in 15.0. And as for
stable branches, the next one is scheduled for early November, so you
have until then to fix typos in those.

For any translations that do not appear in 15.0, you have three more
months until 15.1 ... and so on.

It never ends. Blessing or curse?

Even if it's a curse, it is easily gone by just stopping.. but..

I have refrained from committing too frequently to the repo. (Still it
might a bit too often..) If it is not a problem to commit at most once
per day, things will get a bit easier to me.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center