On 3/12/2016 1:42 AM, Ezio Melotti wrote:
On Sat, Mar 12, 2016 at 12:09 AM, Terry Reedy wrote:
The weeky 'Summariy of Python tracker Issues' ('tracker' should be
capitalized if 'Issues' is) starts with
Content-Type: text/plain; charset="us-ascii"
Names sometimes have not-ascii chars, and they do not get properly displayed
for me with Thunderbird on Windows. For instance,
Raúl Núñez de Arenas (Raúl Núñez de Arenas)
is transmitted as
Ra=C3=BAl N=C3=BA=C3=B1ez de= Arenas
and displayed as
RaÃºl NÃºÃ±ez de Arenas
This already looks like UTF-8 -- you should be able to verify this by
manually selecting UTF-8 as encoding from the menu.
I found the per-message setting and selecting utf-8 fixed it.
If the Content-Type still uses us-ascii though, it should be fixed to
specify UTF-8 instead.
Email from the tracker specifies utf-8. Thunderbird must assume latin-8
for non-ascii in a message specified as ascii.
Terry Jan Reedy
Python-Dev mailing list