From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
cc: pgsql-translators@lists.postgresql.org
Subject: Re: requiring all .po files be UTF8-encoded
In-reply-to: <202512101549.tx3ejz5cr77v@alvherre.pgsql>
References: <202512101549.tx3ejz5cr77v@alvherre.pgsql>
Comments: In-reply-to =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
	message dated "Wed, 10 Dec 2025 17:47:49 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <644237.1765386401.1@sss.pgh.pa.us>
Date: Wed, 10 Dec 2025 12:06:41 -0500
Message-ID: <644238.1765386401@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/644238.1765386401%40sss.pgh.pa.us>
Precedence: bulk

=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de> writes:
> There's an ongoing project to add a regression test to ensure all
> platforms are correctly handling translations. [1]
> [1] https://postgr.es/m/b292844.1765315339@sss.pgh.pa.us

For the list archives' sake: that link seems wrong.  A more
relevant discussion for translation purposes is

https://www.postgresql.org/message-id/flat/292844.1765315339%40sss.pgh.pa.us

in which we discovered that Solaris' gettext implementation
doesn't handle transcoding of .mo files, and that we have to
know at build time which encoding they're in so as to create
appropriate symlinks.  Rather than write code to extract that
information, I proposed that we just institute a policy that
all our .po files should be in UTF-8.  We're apparently nearly
there already so far as actively-maintained .po files go.

			regards, tom lane