LucidTranslations
Revision 2 as of 2009-11-17 17:45:14
Clear message
Discussion Topics
Feedback from last cycle
Rosetta Problems
- Kubuntu packagers have to maintain .pot generation infrastructure
- Kubuntu packagers have to deal with broken upstreams (even for universe packages)
Kubuntu packagers have to deal with upstream <-> downstream translation mismatches (notably .desktop translations)
- There is no way of knowing if our recreation of upstream's .pot generation is at all accurate (there are places I know it isn't) so no way of knowing for sure if ubuntu language packs are better or worse than upstreams
- Past problems have ment some languages have no translators for Kubuntu stuff, e.g. German (I'm told)
- strings get changed from upstream for no reason
- unclear current status of launchpad translations communities generally
- .desktop translations only come from upstream not the packaging
- kde-l10n-xx isn't installed by default so no translated docs or media files
- when .pot files are moved they need changed in rosetta manually. How well is this working?
- generally annoys upstream ("we're not good enough for you?")
Problems with dropping Rosetta
So some Kubuntu developers want to drop it. This also causes problems
- unclear how to ship translations from KDE apps not in main KDE modules
- notable changes would need to be made to pkgbinarymangler and probably to language pack generation
- Strings added by our patches would have no chance of being translated (proposed to have them translated upstream)
- Kubuntu specific programmes still need translated
- wibble