public inbox for [email protected]help / color / mirror / Atom feed
jp.po file mistakes on REL_17_STABLE branch 3+ messages / 3 participants [nested] [flat]
* jp.po file mistakes on REL_17_STABLE branch @ 2025-01-31 14:10 Aya Iwata (Fujitsu) <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Aya Iwata (Fujitsu) @ 2025-01-31 14:10 UTC (permalink / raw) To: pgsql-translators; +Cc: [email protected] <[email protected]> Hi, I found some ja.po file mistakes on REL_17_STABLE branch. This issues were originally found by Yadav, Siddharth san. Issue Breakdown: 1. Added Messages • File: src/bin/psql/po/ja.po • Message: Issue: This message was added in the translation update commit (6bf5bf11c39) to the psql/po/ja.po file[1], but it is not present in the actual source code of OSS[2]. #: describe.c:3080 msgid "Not-null constraints:" msgstr "非NULL制約:" 2. Deleted Messages • File: src/bin/psql/po/ja.po • Message: Issue: This message was marked as deleted in the translation update commit (6bf5bf11c39) in the psql/po/ja.po file[3]. However, it is still present in the actual OSS source code[4]. #: ../../port/user.c:43 ../../port/user.c:79 #, c-format msgid "could not look up local user ID %d: %s" msgstr "ローカルユーザーID %dの参照に失敗しました: %s" 3. Modified Messages • File: src/backend/po/ja.po • Message: Issue: The message was marked as modified in the translation update commit[5], but the original message in the OSS source code has not been changed[6]. #: access/transam/xlog.c:4406 access/transam/xlog.c:4416 #, c-format - msgid "The database cluster was initialized with CATALOG_VERSION_NO %d, but the server was compiled with CATALOG_VERSION_NO %d." - msgstr "データベースクラスタは CATALOG_VERSION_NO %d で初期化されましたが、サーバーは CATALOG_VERSION_NO %d でコンパイルされています。" + msgid "The database cluster was initialized with %s %d, but the server was compiled with %s %d." + msgstr "データベースクラスタは %s %d で初期化されましたが、サーバーは %s %d でコンパイルされています。" I have heard that there may be other similar issues. [1] https://github.com/postgres/postgres/blob/REL_17_STABLE/src/bin/psql/po/ja.po#L1686 [2] https://github.com/postgres/postgres/blob/REL_17_STABLE/src/bin/psql/describe.c [3] https://github.com/postgres/postgres/commit/6bf5bf11c3944886225778790bf35aaff3b12a34#diff-9903b5f122... [4] https://github.com/postgres/postgres/blob/REL_17_STABLE/src/port/user.c#L43 , https://github.com/postgres/postgres/blob/REL_17_STABLE/src/port/user.c#L79 [5] https://github.com/postgres/postgres/blob/REL_17_STABLE/src/backend/po/ja.po#L2315 [6] https://github.com/postgres/postgres/blob/REL_17_STABLE/src/backend/access/transam/xlog.c#L4400 Best regards, Aya Iwata Fujitsu ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: jp.po file mistakes on REL_17_STABLE branch @ 2025-02-07 08:19 Peter Eisentraut <[email protected]> parent: Aya Iwata (Fujitsu) <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Peter Eisentraut @ 2025-02-07 08:19 UTC (permalink / raw) To: [email protected] Hi, These all look like standard issues that arise as the source code changes and in some cases some patches in the source code were reverted. You can download the current translation files from https://babel.postgresql.org/, fill in the missing strings, and delete obsolete ones, and send them in. Thanks. On 31.01.25 15:10, Aya Iwata (Fujitsu) wrote: > Hi, > > I found some ja.po file mistakes on REL_17_STABLE branch. > This issues were originally found by Yadav, Siddharth san. > > Issue Breakdown: > 1. Added Messages > > • File: src/bin/psql/po/ja.po > • Message: > Issue: This message was added in the translation update commit (6bf5bf11c39) to the psql/po/ja.po file[1], but it is not present in the actual source code of OSS[2]. > > #: describe.c:3080 > msgid "Not-null constraints:" > msgstr "非NULL制約:" > > > 2. Deleted Messages > • File: src/bin/psql/po/ja.po > • Message: > Issue: This message was marked as deleted in the translation update commit (6bf5bf11c39) in the psql/po/ja.po file[3]. However, it is still present in the actual OSS source code[4]. > > #: ../../port/user.c:43 ../../port/user.c:79 > #, c-format > msgid "could not look up local user ID %d: %s" > msgstr "ローカルユーザーID %dの参照に失敗しました: %s" > > > 3. Modified Messages > • File: src/backend/po/ja.po > • Message: > Issue: The message was marked as modified in the translation update commit[5], but the original message in the OSS source code has not been changed[6]. > > #: access/transam/xlog.c:4406 access/transam/xlog.c:4416 > #, c-format > - msgid "The database cluster was initialized with CATALOG_VERSION_NO %d, but the server was compiled with CATALOG_VERSION_NO %d." > - msgstr "データベースクラスタは CATALOG_VERSION_NO %d で初期化されましたが、サーバーは CATALOG_VERSION_NO %d でコンパイルされています。" > + msgid "The database cluster was initialized with %s %d, but the server was compiled with %s %d." > + msgstr "データベースクラスタは %s %d で初期化されましたが、サーバーは %s %d でコンパイルされています。" > > I have heard that there may be other similar issues. > > [1] https://github.com/postgres/postgres/blob/REL_17_STABLE/src/bin/psql/po/ja.po#L1686 > [2] https://github.com/postgres/postgres/blob/REL_17_STABLE/src/bin/psql/describe.c > [3] https://github.com/postgres/postgres/commit/6bf5bf11c3944886225778790bf35aaff3b12a34#diff-9903b5f122... > [4] https://github.com/postgres/postgres/blob/REL_17_STABLE/src/port/user.c#L43 , https://github.com/postgres/postgres/blob/REL_17_STABLE/src/port/user.c#L79 > [5] https://github.com/postgres/postgres/blob/REL_17_STABLE/src/backend/po/ja.po#L2315 > [6] https://github.com/postgres/postgres/blob/REL_17_STABLE/src/backend/access/transam/xlog.c#L4400 > > Best regards, > Aya Iwata > Fujitsu ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: jp.po file mistakes on REL_17_STABLE branch @ 2025-02-07 09:21 Álvaro Herrera <[email protected]> parent: Peter Eisentraut <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Álvaro Herrera @ 2025-02-07 09:21 UTC (permalink / raw) To: Peter Eisentraut <[email protected]>; +Cc: [email protected] On 2025-Feb-07, Peter Eisentraut wrote: > You can download the current translation files from > https://babel.postgresql.org/, fill in the missing strings, and delete > obsolete ones, and send them in. Note that you don't have to search for obsolete messages specifically; the message extraction system puts them aside at the end of each file. Those lines start with #~ and you can just remove them. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2025-02-07 09:21 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-01-31 14:10 jp.po file mistakes on REL_17_STABLE branch Aya Iwata (Fujitsu) <[email protected]> 2025-02-07 08:19 ` Peter Eisentraut <[email protected]> 2025-02-07 09:21 ` Álvaro Herrera <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox