A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2016-March/143479.html below:

[Python-Dev] Use utf-8 charset for tracker summaries?

[Python-Dev] Use utf-8 charset for tracker summaries? [Python-Dev] Use utf-8 charset for tracker summaries?Terry Reedy tjreedy at udel.edu
Sat Mar 12 03:56:25 EST 2016
On 3/12/2016 1:42 AM, Ezio Melotti wrote:
> On Sat, Mar 12, 2016 at 12:09 AM, Terry Reedy <tjreedy at udel.edu> wrote:
>> The weeky 'Summariy of Python tracker Issues' ('tracker' should be
>> capitalized if 'Issues' is) starts with
>>
>> Content-Type: text/plain; charset="us-ascii"
>> Content-Transfer-Encoding: quoted-printable
>>
>> 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


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4