Fix typo in Vietnamese translation file

Started by Joshua Shanks11 months ago5 messageshackers
Beta feature

Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.

appliessuccessCI history

You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:

docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t52576
psql -h localhost -U postgres

Built from patchset v1 (message #1), September 20, 2026 at 02:38 AM.

Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:

git clone --branch t52576_1 https://github.com/hackorum-dev/postgres.git

In a checkout you already have, add the fork once:

git remote add hackorum https://github.com/hackorum-dev/postgres.git

then, for this patchset and every later one:

git fetch hackorum t52576_1 && git checkout t52576_1

Patchset v1 (message #1) is on t52576_1

Jump to latest
#1Joshua Shanks
jjshanks@gmail.com

Hi,

I was poking around and found a typo

Change "occured" to "occurred" in pg_basebackup error message.

Cheers,
Joshua

Attachments:

t52576_1
0001-Fix-typo-in-Vietnamese-translation-file.patchapplication/octet-stream; name=0001-Fix-typo-in-Vietnamese-translation-file.patchDownload+1-2
#2Chao Li
li.evan.chao@gmail.com
In reply to: Joshua Shanks (#1)
Re: Fix typo in Vietnamese translation file

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’t done that before. Other folks may provide more info.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Chao Li (#2)
Re: Fix typo in Vietnamese translation file

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

#4Joshua Shanks
jjshanks@gmail.com
In reply to: Tom Lane (#3)
Re: Fix typo in Vietnamese translation file

Thanks for the clarification.

On Sun, Nov 2, 2025 at 2:52 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

Show quoted text

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

#5Alvaro Herrera
alvherre@2ndquadrant.com
In reply to: Tom Lane (#3)
Re: Fix typo in Vietnamese translation file

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.
/messages/by-id/90cdfebb-7f95-9166-55ae-a57ad6bac8e1@postgresql.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)