Translations not exported from Rosetta

Bug #289036 reported by David Planella
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

The Rosetta translations of debian-installer do not appear on the Intrepid RC Live CD yet.

In the case of the Catalan team, we have got several new translations and corrections [1], which although they were made well before the Hardy (yes, Hardy) non-langpack translation deadline did not appear in the Live CD back then.

Now with the Intrepid CD I would have expected to see them, but that it is not yet the case. The package does not seem to include the latest translations, even though they are several months old.

Please export the latest Rosetta translation data into the package before the Intrepid release. This will greatly improve the experience of non-English users and make the translators happy to see their work is being used.

Thanks.

[1] Just an example: https://translations.edge.launchpad.net/ubuntu/intrepid/+source/debian-installer/+pots/debian-installer/ca/1/+translate

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Finnish does have the new translations like for Before and After strings.

I do have noted, though, that some improved translations have never made it in. There's eg. one string in the partition wizard which is not in line with the others (different translation for "Guided"), but the fixed translation does not seem to be taken into use.

It might be thus that already translated strings are not checked for changes/improvements by the scripts, ie. only empty slots are filled in from new translations.

Revision history for this message
Colin Watson (cjwatson) wrote :
Download full text (5.4 KiB)

At least some of the translations you care about are, I believe, of strings already translated in Debian. (Please read down to the end of this comment, though.)

debian-installer's translations need to be updated by hand, since they're used before language packs are installed. Updating them wholesale from Launchpad puts me in the position of having to decide which of Debian's translations or Launchpad's translations are better each time I merge updated packages from Debian (i.e. at the start of every release cycle, and often more frequently than that). I'm afraid I simply can't afford to take on this workload for more than 50 languages. I also can't just throw away one side of the merge because (a) the translation changes done in Debian often constitute important bug fixes in the installer (analogous to c-format bugs, except that Launchpad can't check the substitution format here), so I can't throw away the Debian changes; (b) there's obviously no point in me updating translations wholesale from Launchpad if I'm going to throw away the Launchpad changes on merge. I cannot and will not be put in the position where I end up having to act as a proxy for translation changes in Launchpad where the Launchpad translation team did not take care of forwarding their translations upstream. Thus, I settled a long time ago on the position that I would incorporate Launchpad translations for Ubuntu-specific strings, but only use Debian translations for strings that exist there.

Ever since Warty, I have consistently advised all translators who have asked me about this to contribute translations of installer strings that exist in Debian directly to Debian. I realise that this isn't the same as the usual Launchpad translations workflow where it is possible to have translations in Ubuntu first, but I don't see any other way to do it that doesn't impose a completely unacceptable amount of work and linguistic knowledge on the installer team. I believe that the debian-installer translators are generally receptive to and indeed enthusiastic for contributions; the coordinator certainly is, and supports my position on this, so let me know if you have any social problems there and I may be able to escalate them.

I would like this to be documented somewhere for translators, but I don't know where it should be documented. If you do, feel free to write it up and I can review it for accuracy.

None of this applies to those strings which are specific to Ubuntu: at the time of writing, these are a small number of strings in cdrom-detect, partman-auto, partman-crypto, partman-target, pkgsel, and user-setup, and all or almost all of the strings in oem-config and ubiquity. I'd like to get a list of these published automatically but haven't got round to figuring this out yet. It can probably be extracted somehow from patches.ubuntu.com. I updated all these strings from Launchpad a couple of weeks ago.

I also gather that you object to "d'Ubuntu" in the translation you specifically refer to, and believe that it should read "de l'Ubuntu". These strings are part of a category I refer to as "branding", where the string in Debian includes the text "Debian" itself, an...

Read more...

Changed in ubiquity:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.