Comment 13 for bug 565180

The solution at hand is good enough to resolve the particular issue at hand.

There is however a flaw in the translation workflow that lead to this. In general changing upstream translations is like a patch and Kubuntu likes to be very very concerned about whether a patch is necessary and how to carry it out. For maverick we will bring up a full featured patch spec, and I expect that we should work out a workflow a long with the ubuntu translators to move translations in line with the general patching policy we follow.

Such issues as the one presented here are not only horrible from a technical, but also from a social point of view. Upstream is quick on being upset with distributors when it comes to patching, but upstream is even more so when it comes to breaking translations. And as it is, KDE l10n pretty much hates us for how their translations and localizations always go down the drain in Kubuntu (be it for breakage in the infrastructure or translations issues). Any translation hickup that was caused by changes to their translations AND reported at bugs.kde.org is putting additional strain on our upstream relations, and if those relations can't use something, then it is additional strain.

So, this is definitely something to keep on tracking and resolve in mid- to long-term.

Moritz, please don't take this as personal critique, it is really a problem with the workflow at large. Nobody is perfect, but there should be systems in place to prevent us from letting our imperfection hit the user, unfortunately currently that is not the case.
Thank you for resolving this so quickly and bringing your changes to the attention of the KDE l10n team.