Bugzilla – Bug 219709
kickoff partially localized
Last modified: 2006-11-13 12:50:32 UTC
Sorry for filing two bugs at once.. I'm lazy this time of day. Kickoff is not localized. Btw. the nice new yast progessbars are not localized either, I think they're not translated at all actually, but not entirely sure.
Hmm.. looking closer kickoff is partially localized.
In German, the yast progress bar as used for media check is localized ("Verlauf"). I need more detailed info concerning kickoff.
this is about german localisation, right? there is actually a problem with kickoff.. we've changed the strings slightly in their formatting (though not in content), so thats why they no longer apply. Karl, can I sed' this on the lcn repository or will that cause conflicts?
It's Danish localization actually. Kickoff: The tabs are not translated, some of the tab descriptions (tooltips) are not, some are. A lot of the stuff under "Leave" is not localized. Wrt. to the progressbars, I believe the "title" of them are translated. But "downloading.." and "parsing files.." etc. is not.
Dirk, do you mean runnig sed on the .po files containing the translations? I'd rather like to avoid this in the SVN repository. If the change is important, we need a new POT in suse-i18n and ask translators to update their files.
Well, I think working translations are important, especially if they're already there. I don't quite understand why we need a new pot file submitted to the translators. there is no change, just that <u>f</u> has been changed to "&f". if I supply a new pot file, will the updated translations be ready in time?
No, probably not... You must stay away from applying (cosmetical) changes after string freeze. From L10N POV, it would be the best to revert the textual (formatting) change. Within the suse-i18n SVN, I'd really like POT file maintainers to stay away from editing msgid/msgstr texts in PO files (one reason is, that Novell Gloablization Services will override such an editing with there next update--they work directly with the POT files on there own and other translators may operate similar). If you are very sure about some such editing, I'd rather vote to do it in the spec file of your package.
I've added a workaround to the package.