"Swedish" and "Swedish (Sweden)" should be the same language

Yes, german (germany) should also be the same as "german". As Germany's german does not differ from any other german in the world ;)

We are planning to improve that in the future.

As a start, we removed all locales with country codes that are only spoken in a country.

As always, if you have any suggestion about how to handle it in the UI, just add it here.

Cheers.

How about this?

If you have both language "Language-foo" and "Language-foo (Region-bar)", merge all translations made for "Language-foo" into "Language-foo (Region-bar)" and remove "Language-foo" entirely. When there are conflicts, use the translation from "Language-foo (Region-bar)". For languages with several regions, choose arbitrarily. Often it's obvious ("Swedish" should be "Swedish (Sweden)" rather than "Swedish (Finland)"), and if it isn't e-mail a random translator of one of the involved languages and ask (or simply make something up).

Then, only languages with no region specification available (I'd guess Esperanto & friends) retains their regionless name.

This scheme would fall over if there's a language that both exists as a general language and with a region specification, and there's a noticable difference between the general version of the language and the language spoken in a certain region. Whether or not that's the case I have no idea, but it should at least be a lot less common than the current "Swedish" vs "Swedish (Sweden)" problem.

Sure it does. The Swiss don't use the 'ß' character, for instance.

But the default should be "de", and "de_DE" should vanish -- and the same should happen for any other language.

For the UI, I don't think any UI tweaking besides removing the superfluous entries should be necessary.

With Rosetta, we are not adding links to create translations for languages with country code information anymore (except for zh_TW, zh_CN, pt_PT, some en_??, and any other exception people ask us to add).

If there are already .po files, will appear in the interface, but there is no links to create new po files.

In the near future we will develop a way to merge pofiles so the situation is fixed completely.

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/16