Re: New po files in gimp-help repository (and release soonish)

Hi!

On Sun, Mar 27, 2022 at 2:00 PM Piotr Drąg <[email protected]> wrote:

> niedz., 20 mar 2022 o 22:11 Jehan Pagès via gnome-i18n
> <[email protected]> napisał(a):
> >
> > Hi translators!
> >
> > We added our scripts to create a Windows installer for the manual of
> GIMP (project "gimp-help") directly in the repository. We also now have
> scripts to extract the installer strings into po files before merging them
> back. Therefore the strings for the installer are now localizable from the
> `po-windows-installer/` directory (for now only in the `gimp-help-2-10`
> branch, we'll port to `master` branch later):
> https://gitlab.gnome.org/GNOME/gimp-help/-/tree/gimp-help-2-10/po-windows-installer
> >
> > So first a question: what is the process to add these po files to the
> Damned Lies system so that it's translatable by GNOME translation teams?
> >
>
> Hi Jehan,
>
> Letting us know here or at
> https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues is
> enough. I added the new files to Damned Lies, and now translators can
> get on it. :)
>

Awesome. By the way, I was saying in my email that it was in `
gimp-help-2-10` only. But since then I backported the change to `master`
branch too. Did you add from both? :-)


> I have a question though, what is hiding under the variables (%1 and
> %2)? Adding translator comments explaining those would make it easier
> to translate,


Sure.

* In " No suitable GIMP installations were found. %1 can only be installed
when GIMP %2 is already present.", %1 is replaced by the other localizable
string "GIMP Help", and %2 is the minimum version (which will be
major.minor, i.e. "2.10" for instance).

* In "Select all installs for which you want to install %1", %1 is replaced
by the localized version of "GIMP Help".

if it’s technically possible.
>

I just tested. We extract the string with `intltool-extract` with type
`gettext/ini`. Unfortunately the file is not actually an ini file (just
similar), in particular comments start with `;` whereas intltool looks for
comments starting with `#`.

We can still do something by adding a processing step where I'd just remove
`#` line from the InnoSetup lang file before feeding it to InnoSetup (and
using the un-processed file for intltool tricking it into seeing an ini
file). I'll have a look.

Thanks!

Jehan


>
> Best regards,
>
> --
> Piotr Drąg
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot

_______________________________________________
gnome-i18n mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gnome-i18n