hmm ... 43039 helpcontent2 m92 , 41018 helpcontent2 mXX ( first
checkin of the new help ) is the difference I guess
So if I use mXX OOo source (XX 92) with cat+sort thing it might work.
I'll try (and report follows, of course :-)
Not right. In m63 there is helpcontent2 41253 lines.
Where can I
Robert Ludvik wrote:
David Fraser wrote:
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:
localize -m -l sl-SI -f /tmp/myfile-sl-SI.sdf
printed only a few lines ('header' of localize_sl with basic
information) occupated CPU
David Fraser wrote:
Robert Ludvik wrote:
How can I get a SDF file in format:
...
helpcontent2 ... en-US ... String_in english
helpcontent2 ... sl-SI ... String_in slovenian
...
This is a good question!
:-)
I think it would be better to enable localize to leave out the
language in the output if
Robert Ludvik wrote:
David Fraser wrote:
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
Ivo Hinkelmann wrote:
Hi Robert,
Robert Ludvik wrote:
After I run migratel10nhelp.pl I get .xhp files in 2.0/sl/ folder. Did
anyone merge these files with 2.0/01/ XML files? How?
Copy those generated files into a helpcontent2 directory ( over the
English ones ), run an extract and generate a sdf
Hi Robert,
Robert Ludvik wrote:
After I run migratel10nhelp.pl I get .xhp files in 2.0/sl/ folder. Did
anyone merge these files with 2.0/01/ XML files? How?
Copy those generated files into a helpcontent2 directory ( over the
English ones ), run an extract and generate a sdf file like:
