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
I don't know what heppened to my previous message (lost in space)
Ivo Hinkelmann wrote:
information) occupated CPU with 99% and nothing happend for 20 mins
:-) I use SRC680_m94.
Uff ... don't know what happens there. Do you have a file like
myfile-sl-SI.sdf_err writen by the build in gsicheck too
Hi Robert,
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) occupat
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 wit
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 with 99% and nothing happ
Ivo Hinkelmann wrote:
Hi Robert , David
David Fraser wrote:
[...]
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
On 20 April 2005 15:28, David Fraser wrote:
> Yury Tarasievich wrote:
> > On Wed, 20 Apr 2005 14:06:55 +0300, David Fraser <[EMAIL PROTECTED]>
> > wrote:
> > ...
> >
> >> I think it would be better to enable localize to leave out the
> >> language in the output if the translation is not present.
>
Hi Robert , David
David Fraser wrote:
[...]
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 .
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
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
Yury Tarasievich wrote:
On Wed, 20 Apr 2005 14:06:55 +0300, David Fraser <[EMAIL PROTECTED]>
wrote:
...
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
On Wed, 20 Apr 2005 14:06:55 +0300, David Fraser <[EMAIL PROTECTED]> wrote:
...
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 inter
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 wor
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 m
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 fi
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 locali
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:
localize_s
Hi again
migratel10nhelp README says:
...
# What you will get:
# --
# A directory with the localized help files in 2.0 format.
# But please note:
# The files only contain elements that could be
# migrated and that need localization. So you will end
# up with _incomplete_ help files.
19 matches
Mail list logo
