Re: Where to place .pot file? + Hardcoded tab names change?

Am Thu, May 01, 2025 at 10:49:27PM -0300 schrieb Maria Scappini:

> Attached is the updated (and hopefully fixed!) es.po where:
> - missing "&" were added (hopefully all)
> - unnecessary "fuzzy" markings removed
> - rechecked translations and caught some slight errors
> - has the same order and content (?) as the es.po file from the rel-1-8-=
maint branch

Did you maybe grab the wrong file ?

	client/po$ LANG=3Des_ES ./po-stats.sh ./additional-translations/es.po
	./additional-translations/es.po: 5139 mensajes traducidos, 125 traduccion=
es difusas, 336 mensajes sin traducir.

It still contains 125 fuzzied translations (the "fuzzy"
needs to be *removed* from the comment that precedes the
original string :)

> I downloaded and compared the es.po after merge in the rel-1-8-maint bra=
nch
> as you instructed, and there were some entries which my "original" es.po
> (the one I started translating from) file did not have

This can be due to the fact that before merging your
contribution I recreated translatable strings (gnumed.pot)
from the source code so that the latest strings would be
available for translation.

> and things were not in the same order as well...

Order does not matter in that file because for use at
runtime a binary file is generated (es.mo). Order can,
however, make it easier to find missing translations unless
one uses a translation tool which itself makes finding them
easy.

> I started the translation, quite a few months ago when I first wrote, wi=
th poedit
> but quickly found it made things slow and chunky (it skipped around in a=
n unpleasant
> way...). So I continued translation directly in the .po with a text edit=
or, just
> using poedit to compile the .mo files.

I agree poedit can be sluggish and needs getting used to.
There's also a client/po/create-gnumed_mo.sh which you can
use to turn es.po into es.mo ...

> About the unicode sequences:
>
> msgid "\\u2192 &Clipboard as\\u2026"
> msgstr "\\u2192 &Portapapeles como\\u2026"
>=20
> ... to...
>=20
> msgid "=E2=86=92 &Clipboard as=E2=80=A6"
> msgstr "=E2=86=92 &Portapapeles como=E2=80=A6"

That will certainly work as well. It is IMO even preferable
because just might want to translate the unicode symbol as
well (can be done with the escapes, too, no sweat, but
requires looking up the original sequence meaning first.

Oh, wait, it will likely need to be

> msgid "\\u2192 &Clipboard as\\u2026"
> msgstr "=E2=86=92 &Portapapeles como=E2=80=A6"

however because gettext will search the mo file for the
exact source code string ... (the translation can be pretty
much anything, though).

Regards,
Karsten
=2D-=20
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B