Re: requiring all .po files be UTF8-encoded

On Fri, Dec 12, 2025 at 02:04:45PM +0100, Alvaro Herrera wrote:
> 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.

So do you pull into the translation tree the .po files generated in
the main Postgres repository on a regular basis? As far as I can see
from the commit history, that's what is happening.

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

Yes, I'd be interested to look at what you have, for inspiration. At
least it would be good to not have to duplicate the work that's
required to copy the files from the main tree after a update-po back
to the translation repo. The names of the .po files in the
translation repo are based on the paths to the .po files in the main
tree, as far as I can see.
--
Michael