[Pkg-isocodes-devel] unfuzzying PO files

[Christian Perrier]

Quoting Kamal Mostafa (kamal at whence.com):

> Weird-looking is one thing, but if my change makes update-po generate  
> *new* fuzzy-matched msgstr's that are obviously incorrect, should I  
> really not revert those new msgstr's in the .po's?   How could I check  
> in the new .po file, knowing full well that I am introducing new data  
> which I *know* is incorrect?   MT-53 is simply *not* "Santa Cruz de  
> Tenerife", no matter what the fuzzy matcher might think!  ;-)


Sure. I was more talking about a matter of principles. As translator,
I really hate when maintainers think they can touch or change my
translations, so as maintainer I always try to avoid this..:-)

What we should indeed do (but we discussed that with Tobias) is
maybe disabling fuzzy matching in Makefiles for the update-po
targets....


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-isocodes-devel/attachments/20080316/f889b041/attachment.pgp