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

[Draft] Request for translation updates in Debian packages

Please review this e-mail, I intend to send it to d-d-a "soon"


Hi fellow DDs,

First of all, I wish you all a happy New Year (at least for those who have
started it recently)

On behalf of the Debian Internationalisation team members I would like to
bring to your attention the fact that there are some popular packages that
have had (po-debconf) translations submitted for them and are sitting on the
BTS waiting for the maintainer to upload them (or for somebody to make an
NMU) [1] even after Christian Perrier's NMU campaign [2]

As we are on 'freeze' now and one of the things DDs *can* do during the
freeze is to upload new translations (or translation updates), we would like
to ask all Debian Developers to please upload all translations or translation
updates available in the BTS as soon as possible. 

That way users (our priority) which are not fluent in English would have a
chance to configure their systems using their native tongue. Thanks to the
work of the translation teams many different users can now do a base
installation of Debian on their mother language [3] and we would like to extend
this as much as possible.

If possible, we would like you also to:

* use the 'podebconf-report-po' tool (available in the po-debconf package) to
  notify old translators in case there have been some changes in the
  packages' templates that demand a translation update.

* ask in the debian-i18n mailing list for new translations before any of these
  uploads. If there is an upload going to happen soon for a package some
  translation team coordinators might take some time off their busy schedule
  [4] to provide you with a translation into a new language. That way, your
  uploads will include as many languages as possible.

* give some time (a week) for updates and new translations to arrive before
  making an upload.

That would reduce the number of uploads required to fix l10n-related bugs, as
it would reduce the chances of a package being uploaded fixing l10n bugs and
receiving a new l10n bug shortly after.

We wold be really happy if all the Debian Developers made uploads to try to
fix *all* outstanding l10n-bugs before the Debian 3.1 'etch' release.
Unfortunately, there are many packages with l10n bugs open, some even having
bugs over a year old and some having over 5 different translations
waiting for inclusion in the BTS [5]

Most of the work done by translation teams will be useless if  po-debconf
translations are sitting in the BTS and do not get applied until *after* the


Javier Fernandez-Sanguino

[1] Full list is of l10n bugs is:
(unfortunately, it's not easy to group by package or sort by popularity
without doing some perl-foo)

[2] Which started in october last year until december, and focused on
packages that have at least one pending l10n bug since more than 100 days.
These packages are sorted according to popularity and age on
It followed the procedure described in

[3] See http://d-i.alioth.debian.org/l10n-stats/
The initial (d-i) installation is fully translated to 56 languages and
the base installation is fully translated to 22.

[4] Many are now busy updating the translations of the D-i manual and Release 

[5] There are 1274 l10n bugs (412 of these over a year old, ~800 with a
patch) and 600 of the total follow the [INTL:xx] format so they are most
probably po-debconf translations which are waiting for inclusion.

You can find all the culprits with:

$ wget "http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag&data=l10n&archive=no&ve+rsion=&dist=unstable&pend-inc=pending&pend-exc=pending-fixed&pend-exc=fixed&pen+d-exc=done&include=l10n"; -O - | \
grep "http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg="; | \
perl -ne 'print $1."\n" if /pkg=(.*?)\;/' | sort | uniq -c |sort -nr 

Attachment: signature.asc
Description: Digital signature

Reply to: