[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
Sun Nov 20 19:37:28 EST 2016


Suppose sender is a member who set preference language ja, the list language is french and original From: is 'From: =?UTF-8?B?5LqM5pyoIOmdluS7gQ==?= <futatuki at poem.co.jp>'.
The translation of '%(realname)s via %(lrn)s' is taken from sender's language context, ja, and its charset is euc-jp. The display name of original from cannot encode to iso-8859-1 entirely and translation of 'via' part is miss interpreted as iso-8859-1. For the latter problem, we should encode it to encoding of sender's preference language (at least the translation of 'via' part).

I don't want to break the realname even if it cannot be encoded to
his/her preferred language's encoding, so I select to abandon to
translate 'via' part for simple fix. This will occur in language
settings that of charset/encoding is not UTF-8.

-- 
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