public inbox for [email protected]  

help / color / mirror / Atom feed

From: Guillaume Lelarge <[email protected]>
To: Michael Paquier <[email protected]>
To: Álvaro Herrera <[email protected]>
Cc: [email protected]
Subject: Re: requiring all .po files be UTF8-encoded
Date: Fri, 12 Dec 2025 12:05:26 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

On 12/12/2025 02:14, Michael Paquier wrote:
> On Thu, Dec 11, 2025 at 07:51:33AM +0100, Alvaro Herrera wrote:
>> postgres.po has 6411 strings.  The French translation is currently at
>> 78%, and msgfmt says:
>>
>> 5096 translated messages, 988 fuzzy translations, 327 untranslated messages.
>>
>> My impression is that the postgres.po catalog drops about 8%-10% for
>> each major release.
> 
> Okay, I am new to this business, still I can see what Guillaume has
> been doing in the repo for these things in the fr translation, which
> is pgtranslation/messages.git, with master pointing to upstream
> REL_18_STABLE, I guess.
> 

That's right.

> I am also guessing that most folks just rely on something like po-mode
> on emacs, which is available here:
> https://manpage.me/docs/sharedocs/gettext/gettext_8.html
> 

I don't know about that. I'm using poedit.

> I have quickly tested it and that feels natural, I am not used to the
> shortcuts yet but the docs are pretty clear.
> 
> I have a couple of stupid questions.  What's the flow of a translation
> refresh?  Are the files first generated from the top of a stable
> branch in the main Postgres repository using `make update-po` on a
> periodic basis, then copied back to the translation repository for
> further edits (line number updates, etc.)?  Is it more common to edit
> the existing files in place, without pulling them from the main
> repository?
> 

Sounds more like question for Peter or Alvaro :)

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

There's not really a "good first example". Just pick the first small 
file you can find, and go with it.

Thanks.


-- 
Guillaume Lelarge
Consultant
https://dalibo.com

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: requiring all .po files be UTF8-encoded
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox