From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Isaac To: Jack Hill , guix-devel@gnu.org Cc: guile-email@systemreboot.net, Ricardo Wurmus Subject: Re: Character display problem in mumi and my mail client In-Reply-To: References: Date: Thu, 18 Jul 2019 15:53:41 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" List-Id: Message-ID: <20190718102341.PXR6D3Yxnm8BAuJxdtR7pNPXb9AJ4ja5WNTiHGxbSxQ@z> --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, Thanks for the bug report! > It appears that mumi (or at least the instance of it running on=20 > issues.guix.gnu.org) has problems displaying some non-ASCII characters. I= =20 > noticed it with '=E2=80=99'. Compare > > https://issues.guix.gnu.org/issue/36207 > > with > > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D36207 > > In the former, Ludo's name displays as 'Ludo=C2=A2' while it the latter, = it=20 > displays correctly as 'Ludo=E2=80=99'. > > However, in Ludo's reply the character is displayed correctly. > > Does this indicate that my mail client (alpine on Debian Stretch) is doin= g=20 > the wrong thing? It seems that mumi could handle this situation better=20 > since it debbugs appears to handle it correctly. > > Looking at the raw mail downloaded from debbugs, I see that I'm sending=20 > mail as with the following encoding: > > ``` > Content-Type: text/plain; FORMAT=3Dflowed; CHARSET=3DISO-8859-7 > Content-Transfer-Encoding: 8BIT > ``` > > while Ludo's mail is: > > ``` > Content-Type: text/plain; charset=3Dutf-8 > Content-Transfer-Encoding: quoted-printable > ``` > > Interestingly, when I download the mbox file for my mail from debbugs, an= d=20 > looking at it Emacs with my en_us.UTF-8 locale, the cents-symbol appears.= =20 > Using iconv to convert the file from ISO-8859-7 to UTF8, causes the=20 > correct character to display. So what looks to be happening is that mumi= =20 > is interpreting my messages using the wrong encoding. > > Thoughts? Is this something we want to fix? I think this is a bug in guile-email. On brief examination, I found that guile-email is assuming charset of UTF-8 when the Content-Transfer-Encoding is 8bit. This is incorrect behaviour. I will fix this soon. Regards, Arun. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl0wSK4ACgkQLiXui2GA K7NEkgf/ZwktbhzMLbsft3EiystP0EADDUWNo452cMkEYQwpdnM8wfLqX4W8TEB+ oBFy9pcZZInLdqLnko6Xn1nY7ep91q7iFW3neWT5FZ6Aj+9qVLE0rWnzL59qMTt+ 9WRc4LlLZH5AVTc7nxkJVeDNvPD/gtBvy+hZa4PbQrWXSGH7p2b/tIA8bISrfznv B5gLrAXVWpjsruunSUiDikkK0ajiDRLY7GKvF+JmljXsf9PXzuZ0C07slzb9n48N d6Z6FggwYiECa2sv0hD103JNx/JnZD4JtKEBkl8mmw+uifAsgg56wBk/+S+9XJ+x oPx7D3CGKwwQh0H6ct5fUjJjTDFAqw== =dNXM -----END PGP SIGNATURE----- --=-=-=--