guile-email discussion
 help / color / mirror / Atom feed
From: Arun Isaac <>
To: Jack Hill <>, Ricardo Wurmus <>
Subject: Re: Character display problem in mumi and my mail client
Date: Sun, 28 Jul 2019 13:03:51 +0530	[thread overview]
Message-ID: <> (raw)
Message-ID: <20190728073351.cOhtxMjx4rC6dpofaaRpeK4iRYMCz7-vMrM0QzM_Q9I@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]

> It appears that mumi (or at least the instance of it running on 
> has problems displaying some non-ASCII characters. I 
> noticed it with '’'. Compare
> with

I have fixed this bug. See

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


I think you are using a git checkout of guile-email for the mumi hosted
at 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]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2019-07-28  9:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2019-07-18 10:16   ` [bug] " Arun Isaac
2019-07-18 10:23 ` [guile-email] " Arun Isaac
2019-07-18 10:23   ` Arun Isaac
2019-07-18 10:23   ` Arun Isaac
2019-07-28  7:33 ` Arun Isaac [this message]
2019-07-28  7:33   ` Arun Isaac
2019-07-28  7:33   ` Arun Isaac
2019-07-28  8:36   ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox