© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Mark asks:
Why is charset changed in your example? With Tokio's patch, if DECORATE_MCSET is first...
Petr replies:
I tried the default configuration first. Since it changed the enconding from 8bit to QP, I wasn't testing any other settings since this alone is a no go. Moreover, Tokio's config option again applies to all languages, which is suboptimal, as the non-standard sequence is apparently only needed for Japanese. Thus I believe it should only be restricted to Japanese and not extended to all languages by default. And if most locales will be UTF-8, putting LCSET first renders all the following options useless (never reached).
Mark also wrote:
In short, delivery of messages containing unencoded bytes >x7F is not guaranteed.
These are hard choices in general, but I am reluctant to make changes that would potentially break Mailman altogether, even if only in rare cases.
Petr replies:
When you ultimately want to avoid 7bit->8bit upgrading in Mailman, then there are two alternatives:
1)add the footer as MIME multipart and leave the original message 7bit, or
2)apply my patch with a small modification - instead of
+ else:
+ newcset.
use
+ elif cte=='8bit':
+ newcset.
Which one do you prefer?