Re: Few untranslated error messages in OAuth
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-11-13T12:19:30Z
Lists: pgsql-hackers
> On 13 Nov 2025, at 09:13, Álvaro Herrera <alvherre@kurilemu.de> wrote: > On 2025-Nov-13, Zhijie Hou (Fujitsu) wrote: >> During testing of libpq, I noticed several error messages not processed by >> libpq_gettext, resulting in their exclusion from *.pot files. The attached patch >> wraps these messages. Thanks for the report! > Yeah, this roughly makes sense. I think the documentation for errctx in > async_ctx needs to be updated though, because currently it says "it'll > be translated for you" but this patch makes it the other way around (it > must come translated). +1 > Alternatively, we could mark the strings with gettext_noop(), which only > adds the messages to the catalog without translating them; so the > responsibility of translating them would remain where it is today. This > might be easier. I was pondering that since auth error messages in backend libpq does this, but since we don't use gettext_noop anywhere else in frontend libpq today it makes sense to go with libpq_gettext and update the docs instead. Unless you, who has more translation/nls insights than me, feel strongly about gettext_noop I'll go ahead with the current patch. -- Daniel Gustafsson
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
libpq: Align oauth_json_set_error() with other NLS patterns
- 7a15cff1f111 18.2 landed
- f7fbd02d32c4 19 (unreleased) landed
-
libpq-oauth: Don't translate internal errors
- aac25567fec1 18.2 landed
- 301a1dcf00c8 19 (unreleased) landed
-
libpq: Add missing OAuth translations
- 169ff4ca930b 18.2 landed
- ea3370b18ebe 19 (unreleased) landed