[Pkg-isocodes-devel] unfuzzying PO files
Kamal Mostafa
kamal at whence.com
Sun Mar 16 08:40:44 UTC 2008
Christian Perrier wrote:
> Quoting Kamal Mostafa (kamal at whence.com):
>
>> sk.po - [...]acquired a new translation for MT-53 "Santa Lucija" as "Santa Cruz de Tenerife". I removed those new entries.
>>
> In general, I recommend never ever changing *translations*
My thinking for this case was: The original change is just the removal
of trailing blanks -- no actual "name" information is being added or
removed from any strings. Therefore, no msgstr's should change as a
result (except if it also needs a blank removed), and by the same token,
no msgstr should become fuzzy as a result (or become unfuzzy if it was
fuzzy already).
(Fuzzy thinking for a fuzzy case?)
> even if things look weird to us.
>
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! ;-)
-Kamal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-isocodes-devel/attachments/20080316/946e3712/attachment.htm
More information about the Pkg-isocodes-devel
mailing list