Re: [Tuxpaint-devel] Appstream metainfo file added, removed intltool dependency

[Will T. <wj...@en...>]

Hi,

What version of RHEL are you using? Which version of gettext do you have? I
believed that this change would require gettext 0.19.7, which was released
in Dec 2015.

Ah, actually I have a hunch... It looks like the RHEL 7 version of gettext
may be 0.19.8.1. In that version, only the old name for these files, ending
appdata.xml, is supported, not the newer name, metainfo.xml. So I think at
present the effective minimum gettext version is 0.20. If you can confirm
my hunch with the questions above, and the project desires to support this
platform & gettext version, then I can take a look at reducing the minimum
version required.

– Will


On Tue, 28 Jun 2022 at 15:27, Shin-ichi TOYAMA <dol...@wm...>
wrote:

> Hi!
>
> I noticed that 'make' currently stops on RHELs showing error as follows.
>
> msgfmt --xml -d src/po --template src/
> org.tuxpaint.Tuxpaint.metainfo.xml.in -o
> src/org.tuxpaint.Tuxpaint.metainfo.xml
> msgfmt: cannot locate ITS rules for src/
> org.tuxpaint.Tuxpaint.metainfo.xml.in
> make: *** [Makefile:539: src/org.tuxpaint.Tuxpaint.metainfo.xml] Error 1
>
> How shoud I do for thie?
>
>
>
> On Tue, 14 Jun 2022 01:30:21 -0700, Bill Kendrick wrote:
> >
> >This evening I merged a number of commits from Will Thompson,
> >who has been maintaining the Flathub (Flatpak) version of
> >Tux Paint.
> >
> >  https://sourceforge.net/p/tuxpaint/tuxpaint/merge-requests/12/
> >
> >Some of these concern localization, and POT/PO files were
> >regenerated this evenign as well:
> >
> > * Add appstream metainfo file
> >
> >   This is used by software centres such as GNOME Software to display
> >   information about the app, both before and after it is installed.
> >
> >   ...
> >
> >   Many fields in this file are translatable.
> >
> >   ...
> >
> >   The release notes are taken from the press releases on the Tuxpaint
> >   website. They will be extracted for translation.
> >
> >
> > * Remove intltool dependency
> >
> >   Since gettext 0.19, gettext itself has been able to extract strings
> >   from and merge translations to .desktop files. As a result, there is
> >   no need to use intltool. More details are available on
> >   https://wiki.gnome.org/MigratingFromIntltoolToGettext, though that
> >   page assumes a project using Autotools, which this project does not.
> >
> >   One advantage of using xgettext rather than intltool is that there is
> no
> >   need to prefix translatable keys in the .desktop.in file with _. This
> >   patch adjusts tuxpaint.desktop.in accordingly, which makes the input
> >   file itself a valid desktop file.
> >
> >   ...
> >
> >   POTFILES.in.in must be updated to remove the intltool-specific file
> >   encoding annotation; instead this is passed to xgettext.
> >
> >   Finally, update-po.sh is rewritten to invoke xgettext and msgfmt rather
> >   than intltool commands.
> >
> >   The mangling of POTFILES.in.in to prefix all filenames with '../' is
> >   only necessary to minimize the churn when updating the .pot and .po
> >   files, to simplify review of this change. The alternative is to pass
> >   --directory=.. to xgettext. This would cause all .po files to be
> updated
> >   as follows when regenerated:
> >
> >     #. Response to Black (0, 0, 0) color selected
> >     -#: ../colors.h:86
> >     +#: colors.h:86
> >     msgid "Black!"
> >     msgstr "Noir !"
> >
> >I'm a bit exhausted at this point, but I _think_ this all looks good,
> >and wanted to give a heads-up to translators.
> >
> >Gnite! :)
> >
>
>
> --
> Shin-ichi TOYAMA <dol...@wm...>
>
>
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>