The RFC1522/Header encoding/decoding issues should now be fixed on bugs.debian.org with the last round of patches that I've applied. If you find additional issues with headers that are sent out not being properly encoded, please send additional information to 306068@bugs.debian.org until that bug is closed by the release of a new version of debbugs. If you find issues with pages not being decoded correctly *WHEN THE MESSAGE SENT TO THE BTS WAS ENCODED CORRECTLY*[1] please send more information on them to 46848@bugs.debian.org until that bug is closed as well. Since I'm not an expert on i18n by any means, the more information you give the bug, the more likely any remaining issues will actually be fixed. Don Armstrong 1: There are a few messages in the BTS already that were sent without proper encoding; we assume they are in UTF-8. If they aren't, well, too bad. -- There is no mechanical problem so difficult that it cannot be solved by brute strength and ignorance. -- William's Law http://www.donarmstrong.com http://rzlab.ucr.edu
Attachment:
signature.asc
Description: Digital signature