From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Isaac Subject: Re: Character display problem in mumi and my mail client Date: Sun, 28 Jul 2019 13:03:51 +0530 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: 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 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Jack Hill , Ricardo Wurmus Cc: guix-devel@gnu.org, guile-email@systemreboot.net --=-=-= 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----- --=-=-=--