Martin Schlander
Like in 11.0 with packagekit we again have our own versions of translations for things, that should usually be translated upstream. This time it's
* kcm_knetworkmanager * plasma-applet_networkmanager
Like with packagekit it makes some sense to have our own translations as it's very new stuff with hardly any translations upstream - and at the same time it's stuff that's right in the face of users. But it's still unfortunate due to the risk of duplicate effort and different translations for the same software which can create somewhat of a support nightmare.
Therefore I suggest to check for existing translations in your language for these two applications here, to merge with the openSUSE POs to potentially save some work. http://l10n.kde.org/stats/gui/trunk-kde4/package/playground-base/
And to make a little effort to send your translations to the KDE coordinator for your language when you're done translating, to minimize duplicate work.
Find information about your upstream KDE translation team here: http://l10n.kde.org/teams-list.php
Or go to 'Help -> About <application> -> Translation' in a random KDE app.
Thanks for pointing out. Some more translation files are affected, esp. the gnome files. I'm wondering how we want to manage upstream translations? Stanislav once worked on this issue, but the process is not settled, IIRC. If we'd introduce a flag and a URL reference to the 50-pot/MAINTAINERS file or somewhere else, I could download the upstream translations and merge them somehow with our translations. Remaining questions are which version should win and how we want to resolve concurring translations. Finally, we must decide how to feed upstream and openSUSE community translations into the business products, and, maybe, vice versa. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org