RE: Tajik Language - Adding support for a new language
Hi Christian and Dmitrijs,
Yes, Ubuntu team make all these recommendations to translators and
"It currently not possible to send translations done in Launchpad
automatically back to upstream. For this reason, if translation is only done
in Launchpad, these contributions do not flow back to the original project
and thus other distributions will not be able to benefit from the
translations done in Ubuntu. We want to ensure that as a consumers of the
awesome upstream translations we can give back the equally awesome
contributions of the large Ubuntu translations community. We thus encourage
and rely on the Ubuntu translation teams to fill the gap and send their new
translations and fixes to upstreams".
These all is described in this topic:
https://wiki.ubuntu.com/Translations/Upstream and that is why I was advised
by Dmitrijs to join Debian.
Well, all I want is just to make sure that none of Tajik contributed
translation is lost.
By the way, Dmitrijs do you have a list of specific-ubuntu files so we can
translate only them from the Launchpad and import the other files to
Launchpad from the upstream projects?
Or how specific-ubuntu files can be recognized on the Launchpad?
From: Christian PERRIER [mailto:firstname.lastname@example.org]
Sent: 01 August 2013 13:30
To: Victor Ibragimov
Cc: email@example.com; firstname.lastname@example.org;
Subject: Re: Tajik Language - Adding support for a new language
Quoting Victor Ibragimov (email@example.com):
> But how about Gnome and KDE? Recently, we did a great job for Gnome
> https://l10n.gnome.org/languages/tg/gnome-3-10/ui/, but I still see
> incomplete translations of those 100% files on Debian pages
> http://www.debian.org/international/l10n/po/tg )))). How often PO
> files from the upstream are updated for Debian? Should I update those
> files manually or it is done automatically at a certain time?
It depends on several factors:
1) first of all, what is done in Launchpad has to go upstream
2) then, once upstream incorporates the translation in a new release, that
new upstream release has to be packaged for Debian (and indeed Ubuntu as
Step 1) is something I don't really know how it's working and if even
someone in the Canonical/Ubuntu/Launchpad world guarantuees it really
If it does, fine. If it doesn't, then work is partly lost.
This is precisely the reason for which, we (Debian i18n folks) do NOT
encourage people to work on upstream translation in the downstream
Translation of software has to be done with upstreams: KDE, Gnome,
LibreOffice and (imho) not in distros.
I know Launchpad/rosetta seems appealing, attractive, etc. But as long as
nothing guarantees that localization work done there ends up in upstream
projects (and then later in all distros : Debian, Fedora, RHEM, CentOS,
etc.) I would not encourage anyone to work there *unless the upstream
authors have chosen to use Launchpad as their development and localization
As a consequence, when it comes at Debian i18n, we only focus on things
where Debian *is* the upstream: the installer, our native packages (dpkg,
apt, debconf and dozens of others), our webpages, our communication material
(such as Debian News), etc.
What you mention about Gnome is probably because not all of Gnome 3.10 is in
Debian yet. Transitions for environments such as Gnome and KDE take a very
significant time for packagers to work on them (for instance, KDE 4.10 just
landed in Debian usntable) so that explains why it takes time for your l1n
work to end up in the distribution.