| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Guillaume Lelarge <guillaume(dot)lelarge(at)dalibo(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-translators(at)lists(dot)postgresql(dot)org |
| Subject: | Re: requiring all .po files be UTF8-encoded |
| Date: | 2025-12-12 13:04:45 |
| Message-ID: | 202512121300.n2f42o3wkmdf@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-translators |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-12-14 23:42:17 | Re: requiring all .po files be UTF8-encoded |
| Previous Message | Guillaume Lelarge | 2025-12-12 11:05:26 | Re: requiring all .po files be UTF8-encoded |