Robert Ludvik wrote:This is a good question!How can I get a SDF file in format: ... helpcontent2 ... en-US ... String_in english helpcontent2 ... sl-SI ... String_in slovenian ...
:-)
> I think it would be better to enable localize to leave out the
> language in the output if the translation is not present.
> Then oo2po will pick up that no translation is present and will give > a blank msgstr.
I agree with this one.
But given the current situation, I presume it is producing English in the sl-SL lines because your translations haven't been merged.
You could merge the sl-SL sdf into the source using localize -m and then extract it again using localize -e, but this will still give you some English strings.
I'll try this. If I get it right: localize -m -l sl-SI localize -e -l en-US,sl-SI and this results in SDF format like: ... helpcontent2 ... en-US ... String_in english helpcontent2 ... sl-SI ... String_in slovenian ... if it was migrated translation from 1.x .xhp and ... helpcontent2 ... en-US ... String_in english helpcontent2 ... sl-SI ... String_in english ... if it was *not* migrated translation from 1.x .xhp. After oo2po there would be PO file:
msgid "String_in english" msgstr "String_in slovenian"
msgid "String_in english" msgstr "String_in english"
First pair of msgid/msgstr is a charm and second is OK - we'll have to check and translate all entries but we should do it anyway.
Or you could cat the plain English and plain Slovenian (your version) SDF files together and sort the result, which oo2po should then be able to handle. Note that this may confuse the current release, so please let me know how this works. (It should be OK if you specify the languages on the command line).
I'll try this one too.
Hope that helps David
Thanks -- Robert Ludvik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
