Feedback-ID: ie0a040ee:Fastmail
Message-ID: <99287ccb-b385-4d78-8539-a22b42823792@eisentraut.org>
Date: Fri, 28 Nov 2025 16:18:49 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: translator comments for GUC descriptions useful?
From: Peter Eisentraut <peter@eisentraut.org>
To: "pgsql-translators@postgresql.org" <pgsql-translators@postgresql.org>
References: <1a89b3f0-e588-41ef-b712-aba766143cad@eisentraut.org>
Content-Language: en-US
In-Reply-To: <1a89b3f0-e588-41ef-b712-aba766143cad@eisentraut.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/99287ccb-b385-4d78-8539-a22b42823792%40eisentraut.org>
Precedence: bulk

On 07.11.25 09:53, Peter Eisentraut wrote:
> I've done some work recently in the source code to make the GUC C 
> structs automatically generated.  That now allows changing the output 
> format more easily.
> 
> 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 ""
> 
> (and analogously for the long description).

I have committed this.  (It's only in the master branch right now, so it 
won't be active until the messages git repository is branched, usually 
in February.)