On Mon, Aug 20, 2012 at 05:34:43PM -0400, David Prévot wrote:
> Depending of how much « a few days » are, what do you prefer? If it's
> about ten days or more, I could go now with the first proposal, but if
> it's less than five days (if the fix meet the freeze exception criteria
> of course), or more than eighteen days, the second proposal seems like a
> good plan.

Upstream did not react swiftly to the report, so I went to do an upload
tonight with the translation-only change.  However, I find that the
supplied .po does not pass a lintian check, citing encoding errors.  I'm
cc'ing the bug in case the translator has comment, either because the
file was garbled in translation or because I'm being stupid.

aqua@kesha:~/tinker/debian/qpsmtpd/qpsmtpd-0.84
$ msgfmt --statistics -v -c -o /dev/null debian/po/da.po 
debian/po/da.po:32:39: invalid multibyte sequence
debian/po/da.po:32:59: invalid multibyte sequence
debian/po/da.po:32:65: invalid multibyte sequence
debian/po/da.po:33:50: invalid multibyte sequence
debian/po/da.po:47:66: invalid multibyte sequence
debian/po/da.po:48:30: invalid multibyte sequence
debian/po/da.po:48:46: invalid multibyte sequence
debian/po/da.po:48:62: invalid multibyte sequence
debian/po/da.po:49:25: invalid multibyte sequence
debian/po/da.po:49:38: invalid multibyte sequence
debian/po/da.po:50:3: invalid multibyte sequence
debian/po/da.po:50:20: invalid multibyte sequence
debian/po/da.po:50:67: invalid multibyte sequence
debian/po/da.po:51:10: invalid multibyte sequence
debian/po/da.po:61:3: invalid multibyte sequence
debian/po/da.po:62:40: invalid multibyte sequence
debian/po/da.po:62:44: invalid multibyte sequence
debian/po/da.po:62:69: invalid multibyte sequence
debian/po/da.po:81:17: invalid multibyte sequence
debian/po/da.po:81:46: invalid multibyte sequence
msgfmt: too many errors, aborting


-- 
Devin  \ aqua(at)devin.com, IRC:Requiem; http://www.devin.com
Carraway \ 1024D/E9ABFCD2: 13E7 199E DD1E 65F0 8905 2E43 5395 CA0D E9AB FCD2

Attachment: signature.asc
Description: Digital signature

Reply via email to