Feedback-ID: ie3de48e3:Fastmail
Date: Fri, 7 Nov 2025 10:57:23 +0100
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: "pgsql-translators@postgresql.org" <pgsql-translators@postgresql.org>
Subject: Re: translator comments for GUC descriptions useful?
Message-ID: <202511070940.qinrfzz3gdff@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1a89b3f0-e588-41ef-b712-aba766143cad@eisentraut.org>
Archived-At: 
 <https://www.postgresql.org/message-id/202511070940.qinrfzz3gdff%40alvherre.pgsql>
Precedence: bulk

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/