From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.systemreboot.net (mugam.systemreboot.net [139.59.75.54]) by localhost (mpop-1.4.4) with POP3 for ; Thu, 18 Jul 2019 17:05:03 +0530 Return-path: Envelope-to: arunisaac@systemreboot.net Delivery-date: Thu, 18 Jul 2019 15:53:49 +0530 Received: from localhost.localdomain ([127.0.0.1] helo=[192.168.2.12]) by systemreboot.net with esmtp (Exim 4.92) (envelope-from ) id 1ho3Zl-0001Ye-CA for arunisaac@systemreboot.net; Thu, 18 Jul 2019 15:53:49 +0530 Received: from [14.139.128.10] (helo=steel) by systemreboot.net with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ho3Zf-0001YV-9D; Thu, 18 Jul 2019 15:53:43 +0530 From: Arun Isaac To: Jack Hill , guix-devel@gnu.org In-Reply-To: References: Date: Thu, 18 Jul 2019 15:53:41 +0530 Message-ID: MIME-Version: 1.0 Subject: Re: [guile-email] Character display problem in mumi and my mail client X-BeenThere: guile-email@systemreboot.net X-Mailman-Version: 2.1.29 Precedence: list List-Id: guile-email discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Ricardo Wurmus , guile-email@systemreboot.net Content-Type: multipart/mixed; boundary="===============3930839016850371966==" Errors-To: guile-email-bounces@systemreboot.net --===============3930839016850371966== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= 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/Lwnzx3v3nTLiXui2GAK7MFAl0wSK0ACgkQLiXui2GA K7Pb1Af8DCe4H8dXQAIKs77r1S8UrOtpMiJoX4uLRbY03DeZtS+91S+4pbNbdDPB 9/M4IBcs5Do5w3sLZbATmwHz03pnR03VED7ExKRn14Bn8AGp/Y0JenVbDfuQGPno xjdrY8b5nIaEZHu39DvOTIPKmYOAZcq8NehqmBwbk/9I4VzBDBw8EnX+TmsolqDS kDpNteeVWBwF2p16t+6qdOZ/vpn5cG5Ga7NJ+o2meco9Qstjim+Kznq2UvVvIiio xEo1IJcQ9WM69BzQF1x7Cve+Xnwid86Af+9SU47Vsefa8mYEtrBbdG8y4FUcfaNP oQumE6LVs9GeWg2Dda0mSDRb1/rerQ== =U9h2 -----END PGP SIGNATURE----- --=-=-=-- --===============3930839016850371966== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- guile-email mailing list guile-email@systemreboot.net https://lists.systemreboot.net/listinfo/guile-email --===============3930839016850371966==-- 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----- --=-=-=-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.systemreboot.net (mugam.systemreboot.net [139.59.75.54]) by localhost (mpop-1.4.4) with POP3 for ; Thu, 18 Jul 2019 17:05:03 +0530 Return-path: Envelope-to: arunisaac@systemreboot.net Delivery-date: Thu, 18 Jul 2019 15:54:06 +0530 Received: from [209.51.188.17] (helo=lists.gnu.org) by systemreboot.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1ho3a1-0001Ym-NE for arunisaac@systemreboot.net; Thu, 18 Jul 2019 15:54:06 +0530 Received: from localhost ([::1]:36082 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1ho3Zy-0005yx-SQ for arunisaac@systemreboot.net; Thu, 18 Jul 2019 06:24:02 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:58409) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1ho3Zw-0005yq-HN for guix-devel@gnu.org; Thu, 18 Jul 2019 06:24:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ho3Zu-0004C2-IZ for guix-devel@gnu.org; Thu, 18 Jul 2019 06:24:00 -0400 Received: from mugam.systemreboot.net ([139.59.75.54]:43056) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ho3Zr-00041m-N7 for guix-devel@gnu.org; Thu, 18 Jul 2019 06:23:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=systemreboot.net; s=default; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=KEVIL9snQ2VIUlUTDhGTYkAAAqkljP+SGVPvx8cjac8=; b=FwmDBoytd7gqfBtwAIlLiqmhE B5OD8YWfjseuURv028/F3eyxFlbj+jlLvCToS7Z87v1omy8ovqU0K1cUGZ9Rrv+Xkoz0Tcr/L17rQ osHlEnmiGGvon/tpp78wSd7AciUrZuwKXFq2xhn9EYVLUL/VcGb/2WTrkyTrp1g69brWY=; Received: from [14.139.128.10] (helo=steel) by systemreboot.net with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ho3Zf-0001YV-9D; Thu, 18 Jul 2019 15:53:43 +0530 From: Arun Isaac To: Jack Hill , guix-devel@gnu.org 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" X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 139.59.75.54 X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guile-email@systemreboot.net Errors-To: guix-devel-bounces+arunisaac=systemreboot.net@gnu.org Sender: "Guix-devel" Message-ID: <20190718102341.275nvghyDVQGtBhK5JBD3wW8_OILMOmyNoh_6dmOOjY@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/Lwnzx3v3nTLiXui2GAK7MFAl0wSK0ACgkQLiXui2GA K7Pb1Af8DCe4H8dXQAIKs77r1S8UrOtpMiJoX4uLRbY03DeZtS+91S+4pbNbdDPB 9/M4IBcs5Do5w3sLZbATmwHz03pnR03VED7ExKRn14Bn8AGp/Y0JenVbDfuQGPno xjdrY8b5nIaEZHu39DvOTIPKmYOAZcq8NehqmBwbk/9I4VzBDBw8EnX+TmsolqDS kDpNteeVWBwF2p16t+6qdOZ/vpn5cG5Ga7NJ+o2meco9Qstjim+Kznq2UvVvIiio xEo1IJcQ9WM69BzQF1x7Cve+Xnwid86Af+9SU47Vsefa8mYEtrBbdG8y4FUcfaNP oQumE6LVs9GeWg2Dda0mSDRb1/rerQ== =U9h2 -----END PGP SIGNATURE----- --=-=-=--