Bug 219709

Summary:	kickoff partially localized
Product:	[openSUSE] openSUSE 10.2	Reporter:	Martin Schlander <martin.schlander>
Component:	Translations	Assignee:	Karl Eichwalder <ke>
Status:	RESOLVED FIXED	QA Contact:	Karl Eichwalder <ke>
Severity:	Normal
Priority:	P5 - None	CC:	aj, kde-maintainers
Version:	Beta 2
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	219914

Description Martin Schlander 2006-11-10 02:52:08 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.

Comment 1 Martin Schlander 2006-11-10 02:54:56 UTC

Hmm.. looking closer kickoff is partially localized.

Comment 2 Karl Eichwalder 2006-11-10 10:18:43 UTC

In German, the yast progress bar as used for media check is localized ("Verlauf").

I need more detailed info concerning kickoff.

Comment 3 Dirk Mueller 2006-11-10 11:17:44 UTC

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?

Comment 4 Martin Schlander 2006-11-10 12:55:52 UTC

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.

Comment 5 Karl Eichwalder 2006-11-10 16:01:08 UTC

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.

Comment 6 Dirk Mueller 2006-11-11 23:35:53 UTC

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?

Comment 7 Karl Eichwalder 2006-11-12 06:47:37 UTC

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.

Comment 8 Dirk Mueller 2006-11-13 12:50:32 UTC

I've added a workaround to the package.