11:24 a.m.
Hi,
I am having a small problem with po4a-translate. It seems like it
doesn't recognize the new, translated strings in the .po file.
I translated most of the .po, ran po4a-translate and got the following output:
We found translations for 84.37% (27 from 32) of strings.
Then I decided to translate the rest of the .po. I did that, ran
po4a-translate again and got the exact same output.
It says that only 27 of the 32 strings have been translated, but that
is not correct.
What's up? Am I doing something wrong?
Any help will be greatly appreciated.
--
Runa Sandvik
12:47 p.m.
New subject: [Po4a-devel] po4a-translate does not recognize new strings
Hi,
On Fri, Jul 10, 2009 at 06:24:19PM +0200, runa.sandvik(a)gmail.com wrote:
I am having a small problem with po4a-translate. It seems like it
doesn't recognize the new, translated strings in the .po file.
I translated most of the .po, ran po4a-translate and got the following output:
We found translations for 84.37% (27 from 32) of strings.
Then I decided to translate the rest of the .po. I did that, ran
po4a-translate again and got the exact same output.
It says that only 27 of the 32 strings have been translated, but that
is not correct.
What's up? Am I doing something wrong?
Any help will be greatly appreciated.
This could be caused by:
* an outdated PO file (not synchronized with the current (English)
document)
* a corrupted PO file (e.g. a msgid changed)
* po4a-translate being called with different module options (-o) than
po4a-gettextize
* a po4a bug
If this is not one of the 3 first cases, I would need the english
document, the PO file, and the options for po4a-translate to reproduce
this.
Best Regards,
--
Nekral
1:33 p.m.
New subject: [Po4a-devel] po4a-translate does not recognize new strings
On Fri, Jul 10, 2009 at 7:47 PM, Nicolas
François<nicolas.francois(a)centraliens.net> wrote:
This could be caused by:
* an outdated PO file (not synchronized with the current (English)
document)
* a corrupted PO file (e.g. a msgid changed)
* po4a-translate being called with different module options (-o) than
po4a-gettextize
* a po4a bug
I created the po file again (to make sure that it's new and properly
synced with the current document). I translated the po file (some of
the translations aren't perfect or completed, but every po-string have
a translation) and then tried to run po4a-translate again:
po4a-translate -f wml -m 30seconds.wml -p 30seconds.po -l
no-30seconds.wml -L utf-8 --master-charset utf-8 -v
We found translations for 84.37% (27 from 32) of strings.
30seconds.wml is 84.37% translated (27 of 32 strings).
If this is not one of the 3 first cases, I would need the english
document, the PO file, and the options for po4a-translate to reproduce
this.
I have uploaded the two files here: http://folk.ntnu.no/runasand/po4a/
Also, you'll notice that the three last po-strings in the po file are
translated, but they don't come out as translated in no-30seconds.wml.
I'm not sure why.
Thanks in advance,
--
Runa Sandvik
5:01 p.m.
New subject: [Po4a-devel] po4a-translate does not recognize new strings
Hello,
On Fri, Jul 10, 2009 at 08:33:55PM +0200, runa.sandvik(a)gmail.com wrote:
> If this is not one of the 3 first cases, I would need the english
> document, the PO file, and the options for po4a-translate to reproduce
> this.
I have uploaded the two files here: http://folk.ntnu.no/runasand/po4a/
This was a bug in the Wml module.
It is now fixed in the po4a repository.
If you cannot use the module from the repository, you can also change
30seconds.wml so that it do not contain a non-ASCII char anymore (there
are 2 non-breaking spaces (0xA0), which could probably be changed to
)
Best Regards,
--
Nekral
5:06 a.m.
New subject: [Po4a-devel] po4a-translate does not recognize new strings
On Sun, Jul 12, 2009 at 12:01 AM, Nicolas
François<nicolas.francois(a)centraliens.net> wrote:
This was a bug in the Wml module.
It is now fixed in the po4a repository.
Yay, thank you for fixing this so quickly :)
If you cannot use the module from the repository, you can also
change
30seconds.wml so that it do not contain a non-ASCII char anymore (there
are 2 non-breaking spaces (0xA0), which could probably be changed to
)
Yeah, that works too ;)
--
Runa Sandvik
5610
days inactive
5613
days old
4 comments
2 participants
participants (2)
-
Nicolas François -
Runa Sandvik