[freeciv-i18n] Re: Freeciv po files
[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
On Sat, Aug 31, 2002 at 08:33:51AM +0200, Davide Pagnin wrote:
> On Wed, 2002-08-28 at 11:21, Christian Knoke wrote:
> > On Wed, Aug 28, 2002 at 10:06:11AM +0200, Davide Pagnin wrote:
> > >
> > > There is a problem with actually take this step, many .po files will be
> > > broken if this -c parameter (but this is because they're wrong!) and
> > > thus we need to handle this condition in some way.
> > >
> > > Contacting all translator is one possible thing, but for poorly
> > > maintained .po files, we need something else.
> > Well, is this such a big problem? I found:
> I suspect that you're using old 0.10.X gettext, because the errors
> reported by my 0.11.1 gettext are many more.
> Then my mind really awakened and...
> I've thought: what happens if a make those entries "fuzzy"?
> As someone has already imagined, a fuzzy entry will give no errors, thus
> we have an easy way of reaching the goal (introduction of -c parameter)
> and to preserve work of previous translators, even for unmaintained .po
Good! Maybe there are even other kinds of flags/comments which you could
use (other than fuzzy), just to differentiate it from the fuzzy
> I see no drawback of patching the .po files adding some fuzzy entries
> and I hope that the maintainers will agree with this!
> I've prepared the patch file for the .po files that do not compile on my
> 1.11.1 gettext machine:
> -- Binary/unsupported file stripped by Ecartis --
> -- Type: application/x-bzip
> -- File: full-po-patch.tar.bz2
Can you upload this to incoming?
Christian Knoke * * * http://www.enter.de/~c.knoke/
* * * * * * * * * Ceterum censeo Microsoft esse dividendum.