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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 55158 in the body.
You can then email your comments to 55158 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

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 1 (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 #8 received at 55158 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Benjamin Slade <slade <at> lambda-y.net>, 55158 <at> debbugs.gnu.org
Subject: Re: bug#55158: bug: mu/mu4e on Guix does not use correct
 encoding/utf-8
Date: Sat, 30 Apr 2022 23:11:01 +0200

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

Benjamin Slade schreef op wo 27-04-2022 om 18:22 [-0600]:
> 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.

Does installing glibc-locales + logging in and out again have an
effect?

Greetings,
Maxime.

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 55158 <at> debbugs.gnu.org (full text, mbox):

From: Benjamin Slade <slade <at> lambda-y.net>
To: Maxime Devos <maximedevos <at> telenet.be>
Cc: 55158 <at> debbugs.gnu.org
Subject: Re: bug#55158: bug: mu/mu4e on Guix does not use correct
 encoding/utf-8
Date: Sat, 30 Apr 2022 15:50:23 -0600

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

On Sat, 30 Apr 2022 15:11:01 -0600 (39 minutes, 22 seconds ago), Maxime Devos <maximedevos <at> telenet.be> wrote:

> 
> Benjamin Slade schreef op wo 27-04-2022 om 18:22 [-0600]:
> > 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.

> Does installing glibc-locales + logging in and out again have an
> effect?

> Greetings,
> Maxime.

> 


I've had glibc-locales installed for some time and have rebooted the machines many times. 

Message #14 received at 55158 <at> debbugs.gnu.org (full text, mbox):

From: Benjamin Slade <slade <at> lambda-y.net>
To: 55158 <at> debbugs.gnu.org
Cc: Maxime Devos <maximedevos <at> telenet.be>
Subject: Re: bug#55158: bug: mu/mu4e on Guix does not use correct
 encoding/utf-8
Date: Sat, 07 May 2022 14:23:01 -0600

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

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.)

best,
 —Ben
--

'(Dr Benjamin Slade (he/him)
     ((Linguistics . University of Utah) . <https://linguistics.utah.edu> )
     `(pgp_fp: ,(21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19))
       ((:official-mail . <b.slade <at> utah.edu>)
        (:secure-mail . <slade <at> lambda-y.net>))    
     (:website . <https://lambda-y.net> )
       "sent by mu4e 1.6.10 in Emacs 28.1.50 with org-msg on GNU Guix")

Message #19 received at 55158-done <at> debbugs.gnu.org (full text, mbox):

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.