[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#890664: qa.debian.org: Please integrate w.d.o/intl/l10n statistics extraction within debsources



Package: qa.debian.org
Severity: wishlist
Tags: debsources

Hello,

over 10 years ago, I was one of the main authors of the scripts extracting l10n
informations from all packages.

The page https://www.debian.org/international/l10n/ and all the others
are the result of this opening each and every package of the
distribution, searching for the po files that contain translations.
This way, we can run some stats on these files, so that the
translators can see what they should work on.

In addition, this gives the translators an equipped workflow: files to
translate are extracted and presented in a dashboard (eg,
https://www.debian.org/international/l10n/po/fr). The translators picks these
files from the dedicated page, work on their side to ensure translation and
reviewing in per-language teams (instead of per-package teams that cannot be
manned for every language), and then the translated material is submitted as
patches to the BTS.

The aformentionned dashboard keep track of these BTS submission. See the
current status of the checkinstall package in french in above page. More
examples on the page used by the german team:
https://www.debian.org/international/l10n/po/de

My suggestion is to get rid of the old perl scripts unpacking every packages on
the www infrastructure to extract the po files, and instead integrate it to the
debsource infrastructure.

There is much more that we could do to improve the l10n infrastructure, such as
integrating the weblate service and adding some automatic tools for maintainers
to grab the translations, so that manual interaction with the BTS becomes the
exception.

But these dreams are definitely out of scope, sorry. Even more because I must
be honest: I won't have the energy to do that myself. I'm out of the l10n
business since maybe 10 years. I'm just sad to see that useful piece of our
infrastructure slowly dies. I would love if someone could take care of this,
please.

Thanks in advance,
Mt.


Attachment: signature.asc
Description: PGP signature


Reply to: