Complete.Org: Mailing Lists: Archives: freeciv-i18n: October 2002:
[freeciv-i18n] Stricter gettext error checking (adding -c to msgfmt para
Home

[freeciv-i18n] Stricter gettext error checking (adding -c to msgfmt para

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Freeciv i18n ML <freeciv-i18n@xxxxxxxxxxx>
Subject: [freeciv-i18n] Stricter gettext error checking (adding -c to msgfmt parameters)
From: Davide Pagnin <nightmare@xxxxxxxxxx>
Date: 04 Oct 2002 18:47:14 +0200

        Hi all!

This is an update.

As some of you may remember, the introduction on gettext 0.11.4 and above
of stricter header checking, has suggested me to propose the
adoption (by default) of a more stricter message format checking on the
various po files.

The solution that can keep the work of all translators and let introduce
the stricter -c parameter, is to add a 'fuzzy' marker to any conflicting
entry, so that the work of appropriately fix the problem is left to the
various tranlators team, and the adoption of the -c parameter will not
break cvs compilation.

On a sidenote, I think that all translator have to be urged to start
using the newer version of gettext (at least 0.11.4) because only from
that version some errors are found and you get a proper warning.
(i.e. mismatch in % parameter type and number in plural strings)

Note also that all translators have to be warned to put appropriate
strings in the headers of they po files, with a particular attention of
rules for plurals and charset.

Last, but not least, I suggest all translators to keep 'clean' their po
file, so, after a make xx.pox, remember to delete all the spurious entry
that you can found at the end of the new file (i.e. ~ starting strings).

Comment/Review are Welcomed! :-)

        Ciao, Davide


-- Binary/unsupported file stripped by Ecartis --
-- Type: text/x-patch
-- File: full-po.patch




[Prev in Thread] Current Thread [Next in Thread]