QUOTE(damian @ Jan 6 2006, 19:28)
ok, I have big problem
I've just downloaded WSW and parser said (when I open option dialog) that label urlmapper.tab.label is not defined in settings.xul
but I can't see this label, so what's going on?
Yes, some labels are empty in BabelZilla but in files in locales all are filled, so?
The same effect at my main profile, so currently this extension is broken for polish users - I suppose
I need help
[right][snapback]7955[/snapback][/right]
This is correct but requires some explanation.
When I upload a new version on WTS I remove all new strings that need to be localized so on WTS is simple to see
empty strings.
Take a look at file urlmapper.dtd in polish, this file doesn't exist on
ViewSourceWith.xpi but under WTS appears with all strings empty.
Translator has a visual feedback and sees urlmapper.dtd contains strings to translate.
If you download the urlmapper.dtd you discover that WTS fills all empty strings with english messages.
To test the extension you must merge what arrives from WTS with XPI file.
I knows this is almost complicated so I attach here an xpi with all strings to localize in english but prefixed with three exclamation points so you can find easily where are the messages to translate searching inside files the string
CODE
!!!
I hope this explain because the xpi presents on BZ doesn't contain all strings.
Obviously when I release the version I replace all missing strings with the english one so users (eg polish, russian users) can continue to use VSW.
But they see some messages in polish and other in english an ugly result but that allows to continue to use VSW.
The version 0.0.7.8 downloadable from UMO or from dafizilla contains for polish and russian locale a ugly language mix but it work (the most important thing)
This is the file with polish/english mix [attachmentid=1025] remember every english string inside the polish locale directory is prefixed with three exlamation points.