On Sun, 2014-07-06 at 18:57:35 +0200, Jakub Wilk wrote: > * Guillem Jover <[email protected]>, 2014-07-06, 11:38: > >With the current dpkg git master, i18nspector emits an error on > >man/po/ru.po, for a fuzzy string that contains a conflict marker. I don't > >think fuzzy strings should trigger either errors or warnings, as mentioned > >before in #708586. > > Thanks, fix committed upstream: > https://bitbucket.org/jwilk/i18nspector/commits/155b5602a822
Nice! > If I read the source correctly, the only remaining tag that could trigger > for fuzzy messages is "unusual-character-in-translation". This tag is > usually an indication of broken encoding. At least in some cases, it can be > fixed without the (deep) knowledge of the target language, by people who are > not translators. So I think I'll split this tag into two: one for non-fuzzy > messages; another for fuzzy ones, with severity reduced to pedantic. Does it > sound good to you? Yeah, sounds perfect. Although personally, I would not mind getting broken encoding warnings in all cases, because those usually mess up the editors, and it's something I'd fix myself anyway. But either is fine really. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
