On 2021-09-20 04:14, Matthias Klumpp wrote:
> I still think this is a dumb fix, especially since you loose the
> feature to actually mark strings from being untranslatable by
> dropping the appstream dependency.

And I still don't understand that part of your reasoning.

If appstreams's version of metainfo.its is not present when the POT file
is generated, it falls back to gettext's version which does not extract
<release/> strings at all. And that's what we want to achieve in Ubuntu,
at least as long as GNOME keeps appstream's metainfo.its away when
generating the upstream POT file. Did you see this issue:

https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/149

> A proper workaround would be to leave that in, possibly backport the
> ITS patch for appstream to update the file, and then mark the release
> entries you don't want to have translated with `translate="no"` in
> the XML.

That's a possible way to deal with it in the future once the GNOME
Software maintainer (and all other GNOME project maintainers...) have
reached an agreement with the Damned Lies admins on the matter.

Please note that several `translatable="no"` have already been added:

https://gitlab.gnome.org/GNOME/gnome-software/-/commit/7dc44712

(seems to be effective only for GNOME 41) But the <release/> strings for
40+ are still translatable, so even if the problem is reduced compared
to when I first filed this bug report, it's still present.

If the Damned Lies admins would change their mind, we still have the
problem with the very latest <release/> info. Let's study the release of
gnome-software 40.4 as an example. The NEWS file and the appdata.xml
file were updated in the same commit (surprise, surprise) on August 13:

https://gitlab.gnome.org/GNOME/gnome-software/-/commit/70c23e4a

The actual release HAPPENED ON THE SAME DAY!! So even if those strings
had been passed to the GNOME translators via Damned Lies, the strings
for 40.4 would still have been shipped untranslated. You can't just snap
your fingers to have strings translated. Translators need time.

As you already know, I think it was an unfortunate mistake to consider
the <release/> strings translatable by default. If some project owners
wanted them to be translatable, it would have been much better to give
those projects a possibility to opt in for translation. The maintainers
of projects which opted in could be assumed to be aware of the required
translation workflow for this to make sense.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1927149

Title:
  Irrelevant translatable strings

Status in AppStream:
  Unknown
Status in GNOME Software:
  Unknown
Status in snap-store-desktop:
  New
Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  When building gnome-software on Ubuntu, dh_translations generates a
  translation template (.pot file) to be imported to Rosetta. That
  template includes 700+ log messages from
  data/appdata/org.gnome.Software.appdata.xml.in. The messages are not
  shown to users, and it makes no sense to have those strings
  translated. It's worth mentioning that the strings are excluded in
  upstream's translation template.

  The issue was first reported at the ubuntu-translators mailing list:
  https://lists.ubuntu.com/archives/ubuntu-translators/2021-May/007757.html

  I stripped the redundant strings from the template and uploaded it to
  hirsute manually as a temporary measure.

  The reason why this happens seems to be that the appstream package is
  included in Build-Depends. appstream installs the file
  /usr/share/gettext/its/metainfo.its with rules which make all the log
  entries be extracted. But the gettext package installs
  /usr/share/gettext-0.21/its/metainfo.its with more sensible rules
  which do not make the log entries be extracted. If the former is not
  present, xgettext falls back to the latter.

  So a solution to this issue is to drop appstream from Build-Depends.
  gnome-software seems to build fine without that package (tested in
  PPA).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appstream/+bug/1927149/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to