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 ; Sun, 28 Jul 2019 15:26:48 +0530 Return-path: Envelope-to: arunisaac@systemreboot.net Delivery-date: Sun, 28 Jul 2019 13:04:00 +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 1hrdgt-0002gz-PG for arunisaac@systemreboot.net; Sun, 28 Jul 2019 13:03:59 +0530 Received: from [49.206.11.83] (helo=steel) by systemreboot.net with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hrdgl-0002go-NG; Sun, 28 Jul 2019 13:03:52 +0530 From: Arun Isaac To: Jack Hill , Ricardo Wurmus In-Reply-To: References: Date: Sun, 28 Jul 2019 13:03:51 +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: guix-devel@gnu.org, guile-email@systemreboot.net Content-Type: multipart/mixed; boundary="===============1291272918251129595==" Errors-To: guile-email-bounces@systemreboot.net --===============1291272918251129595== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > 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 I have fixed this bug. See https://git.systemreboot.net/guile-email/commit/?id=3Dac83c2a00c13702bc365c= d0f3074239fa63d743f and https://git.systemreboot.net/guile-email/commit/?id=3D1f7c45fa0b71bd137e4b6= 61e0d473c3eb9c98f48 guile-email's parse-email and parse-email-body functions now prefer to operate on bytevectors, rather than on strings. Likewise, mbox->emails now returns a list of bytevectors, not a list of strings. I have updated the API documentation at https://guile-email.systemreboot.net/manual/Parsing-e_002dmail.html#Parsing= -e_002dmail @Ricardo: I think you are using a git checkout of guile-email for the mumi hosted at issues.guix.info. Could you use the latest guile-email commit on master (specifically, c85e6917ea21631857d93f58e60d910e07317131)? That should fix this bug. No other changes are required in mumi. I will release guile-email 0.2.0 in another week's time. > This reminds me of rjbs's talk, "Email Hates the Living". [0] > > [0] http://yapcasia.org/2011/talk/59 Indeed, email drags along a lot of backward compatibility baggage from the past. In the future, I'll add some of the pathological examples mentioned in this talk as test cases. Also, if you know of any corpus of email parser test cases, please let me know. I will use them to expand guile-email's test suite. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl09T98ACgkQLiXui2GA K7MoywgAy0y8gIqffy2r6eoKSIpf/jgZMPtKAbkcYVu5148tQecrCLdFtnAv7m+D LAGZXueMR8i/ae62/XvQlDrMqdJM5S1zzv5TONkUxED+0oLvP1LmCRt7BggSevI6 I5Laue2GG9RWTys6j7uIPeEswIXzHVXw1/DSP4Trb/fj3y55/rcQwLkBz1K0N32I J/qZr+yTc83oGdrkreTpgJ0oIiqzaZDgG7Xiw5WSqKWhbNrLpg7NIOtpfxPMNBdc u20zeqziz0OTontTYulHO0mTueYc5IXCZyUJ6J1emW6UoKkUYLGhJmy2vdpEyRT2 /yYVahTtK0PWwT0ISid1Qc8YYzX9nQ== =wn96 -----END PGP SIGNATURE----- --=-=-=-- --===============1291272918251129595== 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 --===============1291272918251129595==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Isaac To: Jack Hill , Ricardo Wurmus Cc: guile-email@systemreboot.net, guix-devel@gnu.org Subject: Re: Character display problem in mumi and my mail client In-Reply-To: References: Date: Sun, 28 Jul 2019 13:03:51 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" List-Id: Message-ID: <20190728073351.tm0zRd57q3XBBBFZm7LLW1G0UY4DWtDGGYVlUOqSCLw@z> --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > 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 I have fixed this bug. See https://git.systemreboot.net/guile-email/commit/?id=3Dac83c2a00c13702bc365c= d0f3074239fa63d743f and https://git.systemreboot.net/guile-email/commit/?id=3D1f7c45fa0b71bd137e4b6= 61e0d473c3eb9c98f48 guile-email's parse-email and parse-email-body functions now prefer to operate on bytevectors, rather than on strings. Likewise, mbox->emails now returns a list of bytevectors, not a list of strings. I have updated the API documentation at https://guile-email.systemreboot.net/manual/Parsing-e_002dmail.html#Parsing= -e_002dmail @Ricardo: I think you are using a git checkout of guile-email for the mumi hosted at issues.guix.info. Could you use the latest guile-email commit on master (specifically, c85e6917ea21631857d93f58e60d910e07317131)? That should fix this bug. No other changes are required in mumi. I will release guile-email 0.2.0 in another week's time. > This reminds me of rjbs's talk, "Email Hates the Living". [0] > > [0] http://yapcasia.org/2011/talk/59 Indeed, email drags along a lot of backward compatibility baggage from the past. In the future, I'll add some of the pathological examples mentioned in this talk as test cases. Also, if you know of any corpus of email parser test cases, please let me know. I will use them to expand guile-email's test suite. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl09T+EACgkQLiXui2GA K7MzWgf/U3b//UMQ1ulPBV43N3m2SvCzNU3HQHuSQDR7aonQ+HJVfbdT9zWKIJJu USFLygS4aWYQhrgwoFucP7PpHb/rN9gOrktG8fDNdSErHkQYRwymdVk/sUoC3Ps6 V5L2Kr6CBM+7GjBY1WiOdibfVjMZepjiUwXN0JS39W70t0pw52K892UpAdhtQQoB rKxt+NeyGMwjgdDwcCAvXhpbB70WW/R0kNbbTgzyf186TDkiq2r4wEoP4YCm1JO8 d5Bo8OyGGxKfh0oZx8Qi4fKXPT5HMhrwiLzilob1S8glmwfsh4I9CpOvh5OW4ZWY ICZ4MP40am6yRymIkSXkgFqYr965BQ== =ze7C -----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 ; Sun, 28 Jul 2019 15:26:48 +0530 Return-path: Envelope-to: arunisaac@systemreboot.net Delivery-date: Sun, 28 Jul 2019 13:04:10 +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 1hrdh2-0002h9-WA for arunisaac@systemreboot.net; Sun, 28 Jul 2019 13:04:09 +0530 Received: from localhost ([::1]:43918 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hrdh0-0006Us-6h for arunisaac@systemreboot.net; Sun, 28 Jul 2019 03:34:06 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:51426) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hrdgx-0006UX-FG for guix-devel@gnu.org; Sun, 28 Jul 2019 03:34:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hrdgw-0008Oa-Az for guix-devel@gnu.org; Sun, 28 Jul 2019 03:34:03 -0400 Received: from mugam.systemreboot.net ([139.59.75.54]:55464) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hrdgv-0008Jt-99 for guix-devel@gnu.org; Sun, 28 Jul 2019 03:34:02 -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=4iHzpPvWrmiiFYdDKaDak4pHrsLUz33Wx8rADYSNqYc=; b=jBw1jEJg2nfH/HI+4aU/tNNVg NKVeUhMeC7xnl8RJBPcGNXf3Yo+O1lAPBeIniiWMjRJGHaNa/Sf8+NYPwmyxDCkwvZYVxOITsDCnf aJ/jq0jcurlIhaK5BAjK/0zsDuAt9+u0KaXMU5YXtutF1+xTd4B+mplWZEo4nCtQk0Aak=; Received: from [49.206.11.83] (helo=steel) by systemreboot.net with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hrdgl-0002go-NG; Sun, 28 Jul 2019 13:03:52 +0530 From: Arun Isaac To: Jack Hill , Ricardo Wurmus Subject: Re: Character display problem in mumi and my mail client In-Reply-To: References: Date: Sun, 28 Jul 2019 13:03:51 +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: guix-devel@gnu.org, guile-email@systemreboot.net Errors-To: guix-devel-bounces+arunisaac=systemreboot.net@gnu.org Sender: "Guix-devel" Message-ID: <20190728073351.cOhtxMjx4rC6dpofaaRpeK4iRYMCz7-vMrM0QzM_Q9I@z> --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > 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 I have fixed this bug. See https://git.systemreboot.net/guile-email/commit/?id=3Dac83c2a00c13702bc365c= d0f3074239fa63d743f and https://git.systemreboot.net/guile-email/commit/?id=3D1f7c45fa0b71bd137e4b6= 61e0d473c3eb9c98f48 guile-email's parse-email and parse-email-body functions now prefer to operate on bytevectors, rather than on strings. Likewise, mbox->emails now returns a list of bytevectors, not a list of strings. I have updated the API documentation at https://guile-email.systemreboot.net/manual/Parsing-e_002dmail.html#Parsing= -e_002dmail @Ricardo: I think you are using a git checkout of guile-email for the mumi hosted at issues.guix.info. Could you use the latest guile-email commit on master (specifically, c85e6917ea21631857d93f58e60d910e07317131)? That should fix this bug. No other changes are required in mumi. I will release guile-email 0.2.0 in another week's time. > This reminds me of rjbs's talk, "Email Hates the Living". [0] > > [0] http://yapcasia.org/2011/talk/59 Indeed, email drags along a lot of backward compatibility baggage from the past. In the future, I'll add some of the pathological examples mentioned in this talk as test cases. Also, if you know of any corpus of email parser test cases, please let me know. I will use them to expand guile-email's test suite. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl09T98ACgkQLiXui2GA K7MoywgAy0y8gIqffy2r6eoKSIpf/jgZMPtKAbkcYVu5148tQecrCLdFtnAv7m+D LAGZXueMR8i/ae62/XvQlDrMqdJM5S1zzv5TONkUxED+0oLvP1LmCRt7BggSevI6 I5Laue2GG9RWTys6j7uIPeEswIXzHVXw1/DSP4Trb/fj3y55/rcQwLkBz1K0N32I J/qZr+yTc83oGdrkreTpgJ0oIiqzaZDgG7Xiw5WSqKWhbNrLpg7NIOtpfxPMNBdc u20zeqziz0OTontTYulHO0mTueYc5IXCZyUJ6J1emW6UoKkUYLGhJmy2vdpEyRT2 /yYVahTtK0PWwT0ISid1Qc8YYzX9nQ== =wn96 -----END PGP SIGNATURE----- --=-=-=--