public inbox for [email protected]
help / color / mirror / Atom feedFrom: Daniel Gustafsson <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: Peter Geoghegan <[email protected]>
Cc: Guillaume Lelarge <[email protected]>
Cc: [email protected]
Subject: Re: Is translating server messages really worth it?
Date: Thu, 28 Sep 2023 14:23:21 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAECtzeV6dyu4jTOrorFW=B=EicyejWO7_Seew3Ch0=0wO+M-RQ@mail.gmail.com>
<CAH2-WzkJR2Hx+wvRFVmbe4WaCs93eMm=FcVwqoCRqxswrKpaEQ@mail.gmail.com>
<[email protected]>
> On 27 Sep 2023, at 17:28, Peter Eisentraut <[email protected]> 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
view thread (15+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Is translating server messages really worth it?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox