Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\))
Subject: Re: Is translating server messages really worth it?
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <2a439909-017c-6241-e4f6-a78dc1b373af@eisentraut.org>
Date: Thu, 28 Sep 2023 14:23:21 +0200
Cc: Peter Geoghegan <pg@bowt.ie>,
 Guillaume Lelarge <guillaume@lelarge.info>,
 pgsql-translators@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA0BE8B8-751E-4B92-9FC3-CA59D18B8AD7@yesql.se>
References: 
 <CAECtzeV6dyu4jTOrorFW=B=EicyejWO7_Seew3Ch0=0wO+M-RQ@mail.gmail.com>
 <CAH2-WzkJR2Hx+wvRFVmbe4WaCs93eMm=FcVwqoCRqxswrKpaEQ@mail.gmail.com>
 <2a439909-017c-6241-e4f6-a78dc1b373af@eisentraut.org>
To: Peter Eisentraut <peter@eisentraut.org>
Archived-At: 
 <https://www.postgresql.org/message-id/FA0BE8B8-751E-4B92-9FC3-CA59D18B8AD7%40yesql.se>
Precedence: bulk

> On 27 Sep 2023, at 17:28, Peter Eisentraut <peter@eisentraut.org> =
wrote:

> One specific example of a thing I would like to avoid is that the =
--help output has a wild mix of translated and untranslated lines.

We clearly want to avoid that.

> Of course, this could be avoided by having the whole --help output as =
one translation catalog entry, which is exactly what we have not been =
doing, because that makes it harder to update between versions.

Could we group messages that have all-or-nothing translations required, =
like
--help output, with separate msgctxt contexts?  So "pg_dump --help" =
would be
"msgctxt pg_dump_help_screen" in the po file, which then could be =
analyzed in
order to make the call for including translationfiles or not?

--
Daniel Gustafsson