guile-email discussion
 help / color / mirror / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Jack Hill <jackhill@jackhill.us>, guix-devel@gnu.org
Cc: guile-email@systemreboot.net, Ricardo Wurmus <rekado@elephly.net>
Subject: Re: Character display problem in mumi and my mail client
Date: Thu, 18 Jul 2019 15:53:41 +0530	[thread overview]
Message-ID: <cu7zhlbfxoy.fsf@systemreboot.net> (raw)
Message-ID: <20190718102341.PXR6D3Yxnm8BAuJxdtR7pNPXb9AJ4ja5WNTiHGxbSxQ@z> (raw)
In-Reply-To: <alpine.DEB.2.20.1907171636590.9756@marsh.hcoop.net>

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


Hi,

Thanks for the bug report!

> It appears that mumi (or at least the instance of it running on 
> issues.guix.gnu.org) has problems displaying some non-ASCII characters. I 
> noticed it with '’'. Compare
>
> https://issues.guix.gnu.org/issue/36207
>
> with
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36207
>
> In the former, Ludo's name displays as 'Ludo¢' while it the latter, it 
> displays correctly as 'Ludo’'.
>
> However, in Ludo's reply the character is displayed correctly.
>
> Does this indicate that my mail client (alpine on Debian Stretch) is doing 
> the wrong thing? It seems that mumi could handle this situation better 
> since it debbugs appears to handle it correctly.
>
> Looking at the raw mail downloaded from debbugs, I see that I'm sending 
> mail as with the following encoding:
>
> ```
> Content-Type: text/plain; FORMAT=flowed; CHARSET=ISO-8859-7
> Content-Transfer-Encoding: 8BIT
> ```
>
> while Ludo's mail is:
>
> ```
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: quoted-printable
> ```
>
> Interestingly, when I download the mbox file for my mail from debbugs, and 
> looking at it Emacs with my en_us.UTF-8 locale, the cents-symbol appears. 
> Using iconv to convert the file from ISO-8859-7 to UTF8, causes the 
> correct character to display. So what looks to be happening is that mumi 
> 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.

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

  parent reply	other threads:[~2019-07-18 10:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.20.1907171636590.9756@marsh.hcoop.net>
     [not found] ` <87zhlbg4aw.fsf@elephly.net>
2019-07-18 10:16   ` [bug] " Arun Isaac
2019-07-18 10:23 ` Arun Isaac [this message]
2019-07-18 10:23   ` Arun Isaac
2019-07-18 10:23   ` Arun Isaac
2019-07-28  7:33 ` [guile-email] " Arun Isaac
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=cu7zhlbfxoy.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=guile-email@systemreboot.net \
    --cc=guix-devel@gnu.org \
    --cc=jackhill@jackhill.us \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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