Robert Ludvik wrote:
David Fraser wrote:
The -l option takes two languages, the source and target language.
So try:
oo2po -i myfile-hc2.sdf -o po_dir -l en-US,sl_SL
Note that you don't want -P as these won't be POT files but will have translations...
Hope that helps, let me know if it doesn't work... David
oo2po -i myfile-hc2.sdf -o po_dir -l en-US,sl-SI gives errors "language not found: en-US". Probably because I have only sl-SI in a SDF file.
If I run localize_sl like this:
localize_sl -e -l en-US,sl-SI -f /tmp/myfile
I get two lines (for en-US and sl-SI) but strings are in *both* cases either in english or in slovenian language.
...
helpcontent2 ... en-US ... String_in english
helpcontent2 ... sl-SI ... String_in english
...
helpcontent2 ... en-US ... String_in slovenian
helpcontent2 ... sl-SI ... String_in slovenian
...
grep ^helpcontet2 to myfile-hc2.sdf
and oo2po -i myfile-hc2.sdf -o po_dir -l en-US,sl-SI
puts "String_in slovenian" in msgid and msgstr (which means that oo2po runs OK :-)
How can I get a SDF file in format: ... helpcontent2 ... en-US ... String_in english helpcontent2 ... sl-SI ... String_in slovenian ... Thanks
This is a good question!
I have been making some changes to oo2po and po2oo recently, and this relates to them.
Basically I think the current model where localize includes the English for a language if the translation is not present is not ideal.
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'm interested what others have to hear about this ... Now that localize is a perl script it may be easier to change it, on the other hand we don't want to break existing systems ... It might even be nice to alter localize so that you can give an option to produce / merge PO files directly (doing an internal conversion to sdf using the translate toolkit)
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.
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).
Hope that helps David
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
