Обсуждение: Fix typo in Vietnamese translation file
Hi,
I was poking around and found a typo
Change "occured" to "occurred" in pg_basebackup error message.
Cheers,
Joshua
Вложения
> On Nov 2, 2025, at 04:23, Joshua Shanks <jjshanks@gmail.com> wrote: > > Hi, > > I was poking around and found a typo > > Change "occured" to "occurred" in pg_basebackup error message. > > Cheers, > Joshua > <0001-Fix-typo-in-Vietnamese-translation-file.patch> Looks like the po file has been out of date, the msgid string cannot be found in the source file. Instead of manually updating the po file, I guess some build process (make) could be done to sync the po files, but I haven’tdone that before. Other folks may provide more info. Best regards, -- Chao Li (Evan) HighGo Software Co., Ltd. https://www.highgo.com/
Chao Li <li.evan.chao@gmail.com> writes:
> Looks like the po file has been out of date, the msgid string cannot be found in the source file.
Yeah, I was surprised not to see a fuzz marker there. Apparently
that file hasn't been touched in awhile.
> Instead of manually updating the po file, I guess some build process (make) could be done to sync the po files, but I
haven’tdone that before. Other folks may provide more info.
Indeed, a manual commit of this would be pointless. The master copies
of our .po files are kept in a different git repo that is run by the
pgsql-translation mailing list (and synced to the main project repo
roughly once per release). You'd need to report this there to get
anything productive done about it.
regards, tom lane
Thanks for the clarification.
On Sun, Nov 2, 2025 at 2:52 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Chao Li <li.evan.chao@gmail.com> writes:
> Looks like the po file has been out of date, the msgid string cannot be found in the source file.
Yeah, I was surprised not to see a fuzz marker there. Apparently
that file hasn't been touched in awhile.
> Instead of manually updating the po file, I guess some build process (make) could be done to sync the po files, but I haven’t done that before. Other folks may provide more info.
Indeed, a manual commit of this would be pointless. The master copies
of our .po files are kept in a different git repo that is run by the
pgsql-translation mailing list (and synced to the main project repo
roughly once per release). You'd need to report this there to get
anything productive done about it.
regards, tom lane
On 2025-Nov-02, Tom Lane wrote: > Chao Li <li.evan.chao@gmail.com> writes: > > Looks like the po file has been out of date, the msgid string cannot be found in the source file. > > Yeah, I was surprised not to see a fuzz marker there. Apparently > that file hasn't been touched in awhile. Yeah, the Vietnamese translation files were introduced in 2018 for Postgres 11 and never touched again. https://www.postgresql.org/message-id/flat/90cdfebb-7f95-9166-55ae-a57ad6bac8e1%40postgresql.vn We need a new Vietnamese translator :-( https://babel.postgresql.org/ (Mind, there are many languages that have received insufficient attention in the last few years.) -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "That sort of implies that there are Emacs keystrokes which aren't obscure. I've been using it daily for 2 years now and have yet to discover any key sequence which makes any sense." (Paul Thomas)