Feedback-ID: ia2694551:Fastmail
Date: Wed, 4 Oct 2023 11:10:19 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Peter Eisentraut <peter@eisentraut.org>, Peter Geoghegan <pg@bowt.ie>,
	Guillaume Lelarge <guillaume@lelarge.info>,
 pgsql-translators@lists.postgresql.org
Subject: Re: Is translating server messages really worth it?
Message-ID: <202310040910.g22nzjng3maf@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <FA0BE8B8-751E-4B92-9FC3-CA59D18B8AD7@yesql.se>
Archived-At: 
 <https://www.postgresql.org/message-id/202310040910.g22nzjng3maf%40alvherre.pgsql>
Precedence: bulk

On 2023-Sep-28, Daniel Gustafsson wrote:

> 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?

This is an interesting idea.  So for that kind of thing (help screens)
we would require a very high percentage in order to include it with the
bundle (say 90%), but it would be a very small catalog so easy to
translate; and for other things, say the bulk of server messages, we
would require a lesser percentage in order to be included (even 60%
could be more than good enough IMO).

I'm not sure how that would work, however.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/