gsicheck errors in bg, bs, br, cy, eu, fa, is, ko, sh, sr, and ug

l10n
#1

Hi,

Yesterday I ran gsicheck (a format checker tool) on all extra
localizations, i.e. on lo-build-<lang>.sdf files. I found a few errors
and I fixed all of them.

Owners of the bg, bs, br, cy, eu, fa, is, ko, sh, sr, and ug locales
should check my commit and correct their files in Pootle and/or in their
local archives.

http://cgit.freedesktop.org/libreoffice/build/commit/?h=libreoffice-3-3&id=77b8e1b71cfe3b1201aa9e220057f14cf45df445

Please check your translations regularly, because formatting errors may
prevent integration of translations.

Thanks,
Andras

#2

Thank you for your comment! I just fixed my working copy of KO file which
will be uploaded to Pootle soon. And I will check my translation more
carefully from now on. :slight_smile:

Jeongkyu

#3

Can you give a HOWTO for checking?

#4

I cannot. :frowning: I'm not very familiar to po file based translation. If
Pootle does not check for these problems, then I cannot suggest
anything else.

I'll always run gsicheck before I commit translations.

Best regards,
Andras

#5

Hi,

Yesterday I ran gsicheck (a format checker tool) on all extra
localizations, i.e. on lo-build-<lang>.sdf files. I found a few errors
and I fixed all of them.

Owners of the bg, bs, br, cy, eu, fa, is, ko, sh, sr, and ug locales
should check my commit and correct their files in Pootle and/or in their
local archives.

http://cgit.freedesktop.org/libreoffice/build/commit/?h=libreoffice-3-3&id=
77b8e1b71cfe3b1201aa9e220057f14cf45df445

Please check your translations regularly, because formatting errors may
prevent integration of translations.

Can you give a HOWTO for checking?

I cannot. :frowning: I'm not very familiar to po file based translation. If
Pootle does not check for these problems, then I cannot suggest
anything else.

You have some checks available on Pootle that would normally prevent the break. Under the review tab, if you have some tags that are broken, you will see it here (and several other checks see for French for example
http://translations.documentfoundation.org/fr/libo33/review.html)

I'll always run gsicheck before I commit translations.

If you want to run gsicheck on your file if you work on Pootle, you need first to download the .po/.xlf file, run po2sdf or xliff2sdf, then run gsicheck on the sdf file, correct what is needed, then convert again to upload the file on Pootle or send the .sdf directly to be pushed on git.

Kind regards
Sophie

#6

On 12/15/2010 11:40 AM, skrifaði Sophie Gautier:

Hi,

Yesterday I ran gsicheck (a format checker tool) on all extra
localizations, i.e. on lo-build-<lang>.sdf files. I found a few errors
and I fixed all of them.

Owners of the bg, bs, br, cy, eu, fa, is, ko, sh, sr, and ug locales
should check my commit and correct their files in Pootle and/or in
their
local archives.

http://cgit.freedesktop.org/libreoffice/build/commit/?h=libreoffice-3-3&id=

77b8e1b71cfe3b1201aa9e220057f14cf45df445

Please check your translations regularly, because formatting errors may
prevent integration of translations.

Can you give a HOWTO for checking?

I cannot. :frowning: I'm not very familiar to po file based translation. If
Pootle does not check for these problems, then I cannot suggest
anything else.

You have some checks available on Pootle that would normally prevent the
break. Under the review tab, if you have some tags that are broken, you
will see it here (and several other checks see for French for example
http://translations.documentfoundation.org/fr/libo33/review.html)

I'll always run gsicheck before I commit translations.

If you want to run gsicheck on your file if you work on Pootle, you need
first to download the .po/.xlf file, run po2sdf or xliff2sdf, then run
gsicheck on the sdf file, correct what is needed, then convert again to
upload the file on Pootle or send the .sdf directly to be pushed on git.

Kind regards
Sophie

If you have gettext-tools installed you can run msgfmt
directly on the .po files from command line:
msgfmt --statistics --check /path/to/translated/files

Maybe it does produce the corresponding .mo files, you can
trash those.

Regards,

Sveinn í Felli

#7

I am very familiar with po translation, so also with msgfmt. And if that does
the same checks gsicheck is doing I am fine. I am completely unaware of
gsicheck.
BTW. If you include "-o /dev/null" in the msgfmt command the mo file will not
be produced.