Translations from Pootle pushed to git (for 3.4 rc1), bugs to fix

Hi,

Last night I exported updated po files from Pootle and I pushed them to
git to the translations module. LibreOffice 3.4 rc 1 will contain
these translation updates.

Please note, however, that there are still bugs in your translations
that need to be fixed ASAP.

Locales with bugs:
as, bg, bn, bo, brx, bs, ca-XV, ca, cy, de, dgo, el, eo, fa, fi, gu, he,
hi, hr, id, ka, kk, kn, kok, ks, ku, lt, mai, mk, ml, mn, mni, mr, my,
ne, nl, nn, nr, nso, oc, om, or, pl, pt, ro, rw, sa-IN, sat, sd, sk, sq,
st, sv, ta, te, tg, tn, tr, ts, ug, uk, uz, vi

ca-XV - you uploaded corrupted PO files to Pootle
pt - your help translation contained build breaker bugs

Log files (from all tools) and error files (from gsicheck tool):
http://ftp.fsf.hu/LibreOffice/3.4-rc1-l10nbugs/

I fixed the build breakers in git, but please check all bugs in Pootle
and fix them!

Best regards,
Andras

I have fixed the errors, but how can I know what files are corrupted?

Thanks!

Pau

Hi Pau,

ca-XV - you uploaded corrupted PO files to Pootle

I have fixed the errors, but how can I know what files are corrupted?

For example – if you run Linux – you can test your files with the
following command:

$ for i in `find . -name *.po`;do msgcat $i >/dev/null;done

What tool do you use for translation BTW? Such errors should not
happen with proper tools...
The quote mark was missing after msgstr at some places.

Best regards,
Andras

Hi Andras,

I think i´ve fixed pt. Could You check it?

2011.05.02. 17:52 keltezéssel, Sérgio Marques írta:

Hi Andras,

I think i´ve fixed pt. Could You check it?

Hi Sérgio,

Yes, you have fixed those. But I found a new one. :slight_smile:
sd\source\ui\animations.po has wrong content. It contains the strings
from sd\source\ui\annotations.po.

Regards,
Andras

Hi Andras,

Thanks for that. Fixed.

Regards

Hi,

For example – if you run Linux – you can test your files with the
following command:

$ for i in `find . -name *.po`;do msgcat $i >/dev/null;done

What tool do you use for translation BTW? Such errors should not
happen with proper tools...
The quote mark was missing after msgstr at some places.

I use this sed script to correct some mnemonics. I guess this caused
the error. I have corrected them and reviewed each file. The result of
that order now is «empty», so I guess (hope) it's OK now. Isn't it?

Btw, to search recursively in all directories, I modified the search:
for i in `find * -type f -name "*.po"`;do msgcat $i >/dev/null;done

Thanks!

Pau

vi = fixed

Hi Andras, *,

Andras Timar wrote (02-05-11 15:48)

Log files (from all tools) and error files (from gsicheck tool):
http://ftp.fsf.hu/LibreOffice/3.4-rc1-l10nbugs/

I fixed the build breakers in git, but please check all bugs in Pootle
and fix them!

Thanks for letting know.
Since the more experienced guys are not available atm, can pls someone briefly explain what to fix (what the errors are...)

thanks,
Cor

Hi Cor,

I fixed the build breakers in git, but please check all bugs in Pootle
and fix them!

Thanks for letting know.
Since the more experienced guys are not available atm, can pls someone
briefly explain what to fix (what the errors are...)

Open http://ftp.fsf.hu/LibreOffice/3.4-rc1-l10nbugs/nl.err

In the first line pair you see that there is a bug in
helpcontent2\source\text\swriter\main0110.xhp – this is
https://translations.documentfoundation.org/nl/libo34x_help/swriter.po/translate/

The problem is that source has the tag \<ahelp hid=\".\"\> while
target has \<ahelp hid=\"20515\"\>.

Search for "Selects the current table." and you'll find
https://translations.documentfoundation.org/nl/libo34x_help/swriter.po/translate/?unit=6769806

Correct the error and continue with the next line pair in
http://ftp.fsf.hu/LibreOffice/3.4-rc1-l10nbugs/nl.err

You can also use xmltags check on the Review tab of Pootle. However,
it finds xml tag errors in fuzzy messages, too (i.e. it finds too
many, and errors in fuzzy messages are not relevant).

https://translations.documentfoundation.org/nl/libo34x_help/translate.html?unitstates=translated&matchnames=xmltags
link gives more relevant matches but still more than that we have in
http://ftp.fsf.hu/LibreOffice/3.4-rc1-l10nbugs/nl.err
You can remove the false positives by clicking on the red X next to
the xmltags check name in the open segment.

Best regards,
Andras

Hi Andras,

Your explanation looks great (quickly looking at it). Thanks. I'll have some more time tomorrow to work on it!

Regards,
Cor
Andras Timar wrote (05-05-11 07:06)

H, Andras,

Log files (from all tools) and error files (from gsicheck tool):
http://ftp.fsf.hu/LibreOffice/3.4-rc1-l10nbugs/

Bugs in Turkis are all fixed i think.
http://ftp.fsf.hu/LibreOffice/3.4-rc1-l10nbugs/tr.log

Best regards,
Zeki

Andras Timar wrote (05-05-11 07:06)

Correct the error and continue with the next line pair in
http://ftp.fsf.hu/LibreOffice/3.4-rc1-l10nbugs/nl.err

Is the error in the errors nr. 2 to 6 that e.g. the tag name=\"AutoFormat\" is changed to name=\"AutoOpmaak\" ?

Thanks,
cor

No. The target pages in href="" are different. It is OK to translate
the name attribute.

Best regards,
Andras

Andras Timar wrote (05-05-11 07:06)

The problem is that source has the tag \<ahelp hid=\".\"\> while
target has \<ahelp hid=\"20515\"\>.

So another beginners question: is the first or the second correct?

The second (en-US) is correct.

Hi Andras,

Andras Timar wrote (10-05-11 17:07)

So another beginners question: is the first or the second correct?

The second (en-US) is correct.

Thanks for all your help.

As far as I am aware, the errors are corrected now.

Best,
Cor