[sane-devel] .fr.po - second snapshot - final

[Henning Meier-Geinitz]

Hi,

On Tue, Feb 25, 2003 at 10:50:26PM +0100, Yann E. MORIN wrote:
> So here are the latest translations for french (attached). A little bit of
> improvements thanks to (out of order!) : Stef, Henning and Frank.

Thanks.

By the way, the German translation:
Translated     :  533 (95.2%)  (of which 16 fuzzy ( 3.0%))
Not translated :   27 ( 4.8%)
Total          :  560

> Henning, will you please apply that one? Thanx!

Ok.

make results in:
generating sane-backends.fr.mo from sane-backends.fr.po
sane-backends.fr.po:2098: end-of-line within string
/usr/local/bin/msgfmt: found 1 fatal error

One " missing :-)

> What is the next step in french translations? I plan on getting the .fr.po
> from cvs

Anoncvs is not working currently. And I don't know when and if it will
work again.

> on a regular basis from a cron job, and have it checked against my
> small script, and whenever the number of untranslated/fuzzy messages rise
> above a certain value, I'll have a mail sent to me telling me :
> "Hey boy, move your ass and check the translations for SANE!"
> 
> Would a "0 0 1,16 * *"-job be enough?

I guess it would be enough to check two weeks before every release.
After that data the backends won't change much. Generally, you will
only get major changes if a new backend is included and this backend
does unusual stuff. E.g. the latest addition (ma1509) didn't need any
additional translation because everything was already translated.

> What would be a sensible high-water level for untranslated messages? (10%?)
> And the high-water level for fuzzy translations? (5%?)

That's ok. But I wouldn't be too strict with numbers. If you get the
translation of "Gray" wrong everybody will notice. But nobody may find
out about a wrong translation of "Dither 2x16 squared pattern" that's
only used in a seldomly-used backend. So not only quantity counts.

> How are the fuzzy messages tagged as fuzzy? Subsidiary question : who tags
> them as fuzzy?

#,

Either you do it manually if you aren't sure about the translation or
msfmerge does it when updating the po file from the backends. E.g. if
the untranslated text changes from "Color" to "Colour" the translation
of the original will be made fuzzy. If you think the translation is
correct, just remove the fuzzy marker.

Thanks again.

Bye,
  Henning