| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | "pgsql-translators(at)postgresql(dot)org" <pgsql-translators(at)postgresql(dot)org> |
| Subject: | Re: translator comments for GUC descriptions useful? |
| Date: | 2025-11-07 09:57:23 |
| Message-ID: | 202511070940.qinrfzz3gdff@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-translators |
On 2025-Nov-07, Peter Eisentraut wrote:
> One random idea I had is that we could automatically generate "translator"
> comments on the short and long description strings of GUC parameters. So
> the PO entries could then look like this:
>
> #. translator: GUC huge_pages_status short description
> #: utils/misc/guc_tables.c:5020
> msgid "Indicates the status of huge pages."
> msgstr ""
I like this -- yes, please.
> I suppose the only possible disadvantage is that it would use more vertical
> space.
I don't think this is a problem. Translators are likely using GUI
software (at least those that aren't using Vim or Emacs).
> (Any related ideas while we're here?)
Maybe extract each GUC name and grep all errmsg/errdetail/errhint
strings to make sure the name isn't used verbatim (but only via %s
expansion). (Not really sure to what extent this idea is related to
yours, but it's what I got while looking at guc_parameters.dat.)
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Henson Choi | 2025-11-12 06:54:14 | [PATCH] Fix translation consistency issues in Korean, Chinese Traditional, and Tamil |
| Previous Message | Pavlo Golub | 2025-11-07 09:16:42 | Re: translator comments for GUC descriptions useful? |