Tickets :: Comment on [#9201] Check for ISO-8859-1/Windows-1252 improper charset labeling

* Your Email Address
* Spam protection	Enter the letters below: . .. ..__. __. __. \| \|\|\ \|[__](__ (__ \|__\|\| \\|\| \|.__).__)
Comment	>>> This change seems to fix the conversion issues for me. Although >>> that could just be fortune that we are not doing any ISO-8859-1 >>> conversions in the codepaths I have tested. >> >> I still have problems with the euro sign. >> >> Using IMP : >> compose a new text message and set charset to UTF-8. Send the >> following string : "azerty " >> the received message looks fine in IMP, Thunderbird and Outlook. >> >> compose a new HTML message and set charset to UTF-8. Send the >> following string : "azerty " >> the HTML part looks ok and render just fine in Outlook and >> Thunderbird, but not IMP. I get this with IMP/FF : "azerty â¬" >> >> Looking at the source of the message, the encoded string doesn't look >> the same in the text part : >> >> --=_MgggdEx2InJNFCIGJXUlY0k0 >> Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes >> Content-Description: Plaintext Version >> Content-Disposition: inline >> Content-Transfer-Encoding: quoted-printable >> >> azerty =C3=A2=C2=82=C2=AC >> >> >> --=_MgggdEx2InJNFCIGJXUlY0k0 >> Content-Type: text/html; charset=UTF-8 >> Content-Description: HTML Version >> Content-Disposition: inline >> Content-Transfer-Encoding: quoted-printable >> >> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" >> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> >> <html xmlns=3D"http://www.w3.org/1999/xhtml"> >> <head> >> <!--a75c305b1c0a6022--><title></title> >> </head> >> <body style=3D"font-family:Arial;font-size:14px"> >> <p>azerty =E2=82=AC<br /></p> >> </body> >> </html> >> --=_MgggdEx2InJNFCIGJXUlY0k0-- > > I see exactly the same behavior. And there are actually two errors. > 1) the plain text is double encoded, i.e. the euro sign is turned > into =C3=A2=C2=82=C2=AC while it's still correct in the html part > (=E2=82=AC) > 2) even though it's correct in the mail part, it's not displayed > correctly, i.e. as "â¬"
Attachment
Watch this ticket

Saved Queries