Re: [libreoffice-l10n] gsicheck errors in bg, bs, br, cy, eu, fa, is, ko, sh, sr, and ug

On 15/12/2010 14:30, Andras Timar wrote:
> 2010/12/15 Freek de Kruijf<f.de.kruijf@gmail.com>:
> > Op maandag 13 december 2010 10:26:04 schreef Andras Timar:
> > > 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. :( 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

--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***