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 1qo1e0-00Cp7R-P8 for pgsql-translators@arkaria.postgresql.org; Wed, 04 Oct 2023 13:10:28 +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 1qo1dz-00FGxa-95 for pgsql-translators@arkaria.postgresql.org; Wed, 04 Oct 2023 13:10:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qo1dz-00FGxC-2x for pgsql-translators@lists.postgresql.org; Wed, 04 Oct 2023 13:10:27 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qo1dx-0091pt-1m for pgsql-translators@lists.postgresql.org; Wed, 04 Oct 2023 13:10:26 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 3AE162FABE83 for ; Wed, 4 Oct 2023 15:10:24 +0200 (CEST) Received: from s980.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 29E362E293AD; Wed, 4 Oct 2023 15:10:24 +0200 (CEST) Received: from s471.loopia.se (unknown [172.22.191.6]) by s980.loopia.se (Postfix) with ESMTP id 27B062201690; Wed, 4 Oct 2023 15:10:24 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s980.loopia.se ([172.22.191.6]) by s471.loopia.se (s471.loopia.se [172.22.190.35]) (amavisd-new, port 10024) with LMTP id 1HQKrgXCUs1i; Wed, 4 Oct 2023 15:10:23 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 38.140.183.210 Received: from smtpclient.apple (unknown [38.140.183.210]) (Authenticated sender: daniel@yesql.se) by s980.loopia.se (Postfix) with ESMTPSA id 31AFE220169E; Wed, 4 Oct 2023 15:10:23 +0200 (CEST) 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 In-Reply-To: <202310040910.g22nzjng3maf@alvherre.pgsql> Date: Wed, 4 Oct 2023 15:10:21 +0200 Cc: Peter Eisentraut , Peter Geoghegan , Guillaume Lelarge , pgsql-translators@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <202310040910.g22nzjng3maf@alvherre.pgsql> To: Alvaro Herrera X-Mailer: Apple Mail (2.3696.120.41.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 4 Oct 2023, at 11:10, Alvaro Herrera = wrote: >=20 > On 2023-Sep-28, Daniel Gustafsson wrote: >=20 >> 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? >=20 > 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). >=20 > I'm not sure how that would work, however. Neither do I, I need to educate myself more on the translation infra and process in order to have a better idea if it's at all feasible. I am interested in making it easier to contribute a new translation, or = reboot a stale one, and lowering the overall requirement while keeping the = requirement high on the most relevant bits seem like a way forward. -- Daniel Gustafsson