[Bug 1643210] Re: 'from_is_list' does not RFC2047 encode correctly when translation contains non-ascii char

Yasuhito FUTATSUKI at POEM futatuki at poem.co.jp
Wed Nov 23 23:13:17 EST 2016


Thank you for your better fix. The fix in #10 also works fine for my
environment, except a small issue that it always encodes non-ascii to
UTF-8 even if sender's preferred language is same as list's but its
encoding is not UTF-8.

A test case.
  list's language       : fr (iso-8859-1)
  sender's language     : fr (iso-8859-1)
  sender's display name : =?iso-8859-1?q?G=E9n=E9rales?=
(results)
  From: =?utf-8?q?G=C3=A9n=C3=A9rales_via_Mailman-test?= <...>

Another case.
  list's language       : ja (euc-jp, out going messages are encoded to iso-2022-jp)
  sender's language     : ja (euc-jp, out going messages are encoded to iso-2022-jp)
  sender's display name : =?ISO-2022-JP?B?GyRCRnNMWkx3P04bKEI=?=
(results)
  From: =?utf-8?b?5LqM5pyo6Z2W5LuBIChNYWlsbWFuLXRlc3Qg57WM55SxKQ==?= <...>

It seems to be no problem for almost all MUAs nowadays except some l10n
MUAs (and those MUAs will treat such encoded strings as raw ascii
string, as discribed in RFC, so I think the problem is small).

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1643210

Title:
  'from_is_list' does not RFC2047 encode correctly when translation
  contains non-ascii char

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1643210/+subscriptions


More information about the Mailman-coders mailing list