Robert Ludvik wrote:
Ivo Hinkelmann wrote:
Hi Robert,
Copy those generated files into a helpcontent2 directory ( over the English ones ), run an extract and generate a sdf file like:
localize_sl -e -l en-US -f /tmp/myfile
OK, before this one I had to replace sl-SI with en-US in generated .xhp files, otherwise localize_sl didn't put translated strings from .xhp in /tmp/myfile.
After that grep in your sdf file for all ^helpcontent2 strings and rename 'en-US' to 'sl'
OK, now I have all strings (english and translated) for helpcontent2 module in myfile-hc2.sdf, replaced en-US with sl-SI.
You can generate from your sdf file the POT/PO files, see Pavels blog entry regarding this.
If I use oo2po on myfile-hc2.sdf like
oo2po -imyfile-hc2.sdf -opot_dir -lsl_SI -P
I get translated strings in msgid but I'd like them in msgstr with english strings in msgid :-) How can I get this?
Thanks
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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
