GNU bug report logs - #55158
bug: mu/mu4e on Guix does not use correct encoding/utf-8

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#55158: closed (bug: mu/mu4e on Guix does not use correct
 encoding/utf-8)
Date: Wed, 08 Jun 2022 21:33:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 08 Jun 2022 17:32:13 -0400
with message-id <87r13yj0yq.fsf <at> gmail.com>
and subject line Re: bug#55158: bug: mu/mu4e on Guix does not use correct encoding/utf-8
has caused the debbugs.gnu.org bug report #55158,
regarding bug: mu/mu4e on Guix does not use correct encoding/utf-8
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
55158: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55158
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Benjamin Slade <slade <at> lambda-y.net>
To: bug-guix <at> gnu.org
Subject: bug: mu/mu4e on Guix does not use correct encoding/utf-8
Date: Wed, 27 Apr 2022 18:22:34 -0600

[Message part 3 (text/plain, inline)]

The output of mu [ <https://guix.gnu.org/en/packages/mu-1.6.10/> ] (and thus, by extension, mu4e in Emacs) does not correctly handle characters outside of a certain range (which confuses Emacs to no end). This behaviour occurs both in mu4e and when using mu on the commandline.

For instance, subject lines including the 🎉 emoji ("celebration") do not show the emoji, but rather a backslashed \360. Similar issues occur with, for instance, devanagari characters (Hindi etc.).

When using mu/mu4e on non-Guix systems, this issue does not occur. (I.e. both in mu4e and in mu on the commandline these characters are correctly displayed.)

Since mu depends on xapian, it's possible the issue could also be with Guix's xapian package.

[Message part 4 (message/rfc822, inline)]

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Benjamin Slade <slade <at> lambda-y.net>
Cc: 55158-done <at> debbugs.gnu.org, Maxime Devos <maximedevos <at> telenet.be>
Subject: Re: bug#55158: bug: mu/mu4e on Guix does not use correct
 encoding/utf-8
Date: Wed, 08 Jun 2022 17:32:13 -0400

Hi,

Benjamin Slade <slade <at> lambda-y.net> writes:

> Update: So the encoding issue seems to be at a "lower level" than mu
> in fact. I noticed that new messages come through with the correct
> encoding now, so I assume it was an (odd) issue of locale settings
> when I initialised the mail initially/copied over old messages.
>
> (Unfortunately there does not seem to be a great way to mass re-encode messages. I can use `iconv' to convert, but it fails on messages with attachments, I think.)

OK.  I'm glad you could figure it out at least to some degrees :-).

I'll close the report but if it becomes a problem again feel free to
reopen it, with a reproducer ideally.

Thanks,

Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.