Feedback-ID: ie3de48e3:Fastmail
Date: Fri, 12 Dec 2025 14:04:45 +0100
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Guillaume Lelarge <guillaume.lelarge@dalibo.com>
Cc: Michael Paquier <michael@paquier.xyz>,
	pgsql-translators@lists.postgresql.org
Subject: Re: requiring all .po files be UTF8-encoded
Message-ID: <202512121300.n2f42o3wkmdf@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <36c6a005-b464-4760-ad03-33b6a38be5f7@dalibo.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202512121300.n2f42o3wkmdf%40alvherre.pgsql>
Precedence: bulk

On 2025-Dec-12, Guillaume Lelarge wrote:

> On 12/12/2025 02:14, Michael Paquier wrote:

> > Guillaume, I am likely not going to get that right in the first shot.
> > Would you mind reviewing some of the stuff?  Would it be OK to just
> > send a patch on this list?  If you have a po file that could serve as
> > a good first example, feel free to offer a suggestion or I would just
> > pick up one.  Say only for a couple of entries to get the full idea of
> > how things work.
> 
> I don't mind reviewing, though you should not send a patch. You send the
> whole file. Otherwise, it's a complete nightmare.

This is why I do separate commits with mechanical updates, then further
commits with translation updates.  By separating the two, it's actually
very easy to review the new translations.

I have a bunch of scripts with which I've formed what I find is a
practical workflow for people using old-school text editors.  (I use
Vim, but I imagine they would apply equally well to Emacs).  If anybody
is interested, I can share them.

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