subscription notification mail body
Hi
Subscription notification mail body is also distorted sometimes: I just received one for a new subscriber who used a diacritic in his name. There is '?' (ASCII 0x3F) instead of the character with diacritic.
-- http://people.eisenbits.com/~stf/ http://www.eisenbits.com/
OpenPGP: E3D9 C030 88F5 D254 434C 6683 17DD 22A0 8A3B 5CC0
Stanislaw Findeisen wrote:
Subscription notification mail body is also distorted sometimes: I just received one for a new subscriber who used a diacritic in his name. There is '?' (ASCII 0x3F) instead of the character with diacritic.
I think this is because your list's preferred language is English and Mailman's character set for English is us-ascii so the message body is coerced to ascii and non-ascii characters get replaced by '?'.
If this is a serious issue, you can change Mailman's character set for English to UTF-8 by putting
add_language('en', 'English (USA)', 'utf-8', 'ltr')
in mm_cfg.py.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2012-05-14 01:58, Mark Sapiro wrote:
Stanislaw Findeisen wrote:
Subscription notification mail body is also distorted sometimes: I just received one for a new subscriber who used a diacritic in his name. There is '?' (ASCII 0x3F) instead of the character with diacritic.
I think this is because your list's preferred language is English and Mailman's character set for English is us-ascii so the message body is coerced to ascii and non-ascii characters get replaced by '?'.
If this is a serious issue, you can change Mailman's character set for English to UTF-8 by putting
add_language('en', 'English (USA)', 'utf-8', 'ltr')
in mm_cfg.py.
Why don't we use utf-8 for all languages in Defaults.py?
-- http://people.eisenbits.com/~stf/ http://www.eisenbits.com/
OpenPGP: E3D9 C030 88F5 D254 434C 6683 17DD 22A0 8A3B 5CC0
"Stanisław Findeisen" <stf.list.mailman.dev@eisenbits.com> wrote:
Why don't we use utf-8 for all languages in Defaults.py?
We don't do it for English because of superstitious fear that it will break something for someone.
For non-english the translator determines the character set, and just changing to utf-8 only works for English because ASCII is a proper subset of utf-8.
-- Mark Sapiro <mark@msapiro.net> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
On May 14, 2012, at 08:42 AM, Stanisław Findeisen wrote:
On 2012-05-14 01:58, Mark Sapiro wrote:
Stanislaw Findeisen wrote:
Subscription notification mail body is also distorted sometimes: I just received one for a new subscriber who used a diacritic in his name. There is '?' (ASCII 0x3F) instead of the character with diacritic.
I think this is because your list's preferred language is English and Mailman's character set for English is us-ascii so the message body is coerced to ascii and non-ascii characters get replaced by '?'.
If this is a serious issue, you can change Mailman's character set for English to UTF-8 by putting
add_language('en', 'English (USA)', 'utf-8', 'ltr')
in mm_cfg.py.
Why don't we use utf-8 for all languages in Defaults.py?
I think this would be a good default to change in Mailman 3, once it becomes a Python 3 application (follow up for how you can help with that :). Python 3 gives you a much more sane way of separating and handling unicode and binary data.
Cheers, -Barry
participants (3)
-
Barry Warsaw -
Mark Sapiro -
Stanisław Findeisen