desktop-* (KDE4) and some other PO files not imported at all
david.planella at googlemail.com
Tue Oct 21 19:21:14 BST 2008
2008/10/21 Timo Jyrinki <timo.jyrinki at gmail.com>:
> No, if you upload it as Published upload instead of User upload. The
> uploaded file's translations are marked as being upstream, ie.
> possible Rosetta translations take precedence but all the "empty
> slots" are filled (and the rest can be reverted also back to Packaged
> if there was some work done in Rosetta).
Disclaimer: the following method works, but developers have made it
clear that it is not supported and that they might not be able to give
support in case translators break something due to this workaround.
Actually, the hack consists in uploading the translations *twice*:
once as "User upload" and once as "Published upload". The first
("User") upload is necessary in order to replace the Rosetta strings
with the upstream strings in those cases in which the upstream ones
have changed (e.g. spelling mistake fixes). The second ("Published")
upload is necessary in order to mark all strings as "Published", so
that they can be replaced by those from upstream when automatically
importing newer translations (e.g. at the beginning of the translation
If you forget the first upload, the manually uploaded upstream
translation will only "fill" the missing translations in Rosetta, but
will not replace the existing ones. If you forget the second upload,
the strings you uploaded will never be replaced by those from
We generally avoid this workaround, but there have been occasions in
the past when we have had to make heavy use of them. I believe in this
release we have only done it in two occasions, but we might do it for
evolution if its upstream translation does not get imported in the
next few days.
More information about the ubuntu-translators