Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vHIE5-002lJ0-Gu for pgsql-translators@arkaria.postgresql.org; Fri, 07 Nov 2025 08:53:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vHIE4-00DDdK-6i for pgsql-translators@arkaria.postgresql.org; Fri, 07 Nov 2025 08:53:44 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vHIE3-00DDd8-Uu for pgsql-translators@lists.postgresql.org; Fri, 07 Nov 2025 08:53:44 +0000 Received: from fhigh-b4-smtp.messagingengine.com ([202.12.124.155]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1vHIE1-005sRk-0u for pgsql-translators@postgresql.org; Fri, 07 Nov 2025 08:53:43 +0000 Received: from phl-compute-06.internal (phl-compute-06.internal [10.202.2.46]) by mailfhigh.stl.internal (Postfix) with ESMTP id 424297A0163 for ; Fri, 7 Nov 2025 03:53:40 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-06.internal (MEProxy); Fri, 07 Nov 2025 03:53:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:message-id:mime-version:reply-to :subject:subject:to:to; s=fm2; t=1762505620; x=1762592020; bh=lb Bhr1Gu6jlVgnuy2LUm5M0eASb4uFSkYc1vE+sPJTw=; b=Co4jSUmAZwiQ9u6TFv Jekimel70PVmomnttl6ZVXISGZ8a/kqzAox6kwZMUvBqKQ9K8C90QlTX6GqzqqeB V4FZxeXRyTlcK2IMckYVuQuqHX7+rt0DAzyPJ9WrLxHhn+oaF3QOtfFAIfM7cTDb KvaunQyF+Dy5nw1SMkL5WGU3imioW/osqMEHUoIVl9BqWmMciLUZ7Lr/IMb6Bp4q GjoQUHThzggo8YsEbRoDtk9SgWfXW1Cj3NkqGB1/1UmvFThO2CEnNXHtRA1iJNgF bc+MLGjWpS4tojBIqKd4Vb7iLtNlsiMLvq7w3ZMfwAOqou8uBik+J8TybLn7GD39 4FoA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:message-id:mime-version:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1762505620; x=1762592020; bh=lbBhr1Gu6jlVgnuy2LUm5M0eASb4uFSkYc1 vE+sPJTw=; b=q3IIC+/8FR1eN+C3qkG/0UffFZvhEdlEfpfu1KN0M0Z0KSMMZDx 2k8QovcfEEzImvdctehUB90S71vfPXUVSh0m0z/GX6lTqU7dXPM+8hdjBdNPKkHP yjkMUTGE6Tb2GOC2W2z/GpeoZ14F+8TxMFpfSrB9TF1fnqf60QfFgqIB9CE+AC3x i8TsUVWLaMmFh9n8Ne77hWjuRoVjgJX0JSPD8WesVpnlCNTdKMOkxEBP6RtYBHEe GlbQ/I6Cz8E+tW2/LY5qdEPc0dmz+E54AKVYzruBG1j0Po/j4QQ/nzmgRkBXYaGk M9cnRsZEgljInQF5vlqu5A2Fjh5FTBayU+Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddukeelvdefucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfhuffvtgfgsehtjeertddtvd ejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghrsegvihhs vghnthhrrghuthdrohhrgheqnecuggftrfgrthhtvghrnhepffetvedutdefleejveekge efteffueeugefgfeegkedvudelveelheduffdvveehnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhesvghishgvnhhtrhgruhhtrd horhhgpdhnsggprhgtphhtthhopedupdhmohguvgepshhmthhpohhuthdprhgtphhtthho pehpghhsqhhlqdhtrhgrnhhslhgrthhorhhssehpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 7 Nov 2025 03:53:39 -0500 (EST) Message-ID: <1a89b3f0-e588-41ef-b712-aba766143cad@eisentraut.org> Date: Fri, 7 Nov 2025 09:53:38 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US From: Peter Eisentraut Subject: translator comments for GUC descriptions useful? To: "pgsql-translators@postgresql.org" Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi all, 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). This would be trivial to implement now (see below for an example). Would this be useful? I suppose the only possible disadvantage is that it would use more vertical space. (Any related ideas while we're here?) diff --git a/src/backend/utils/misc/gen_guc_tables.pl b/src/backend/utils/misc/gen_guc_tables.pl index 601c34ec30b..25aa98debed 100644 --- a/src/backend/utils/misc/gen_guc_tables.pl +++ b/src/backend/utils/misc/gen_guc_tables.pl @@ -62,6 +62,7 @@ sub print_table printf $ofh "\t\t.name = %s,\n", dquote($entry->{name}); printf $ofh "\t\t.context = %s,\n", $entry->{context}; printf $ofh "\t\t.group = %s,\n", $entry->{group}; + printf $ofh "\t\t/* translator: GUC %s short description */\n", $entry->{name}; printf $ofh "\t\t.short_desc = gettext_noop(%s),\n", dquote($entry->{short_desc}); printf $ofh "\t\t.long_desc = gettext_noop(%s),\n",