[-- Attachment #1: Type: text/plain, Size: 740 bytes --] 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.
[-- Attachment #1: Type: text/plain, Size: 913 bytes --] 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. [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 260 bytes --]
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --] On Sat, 30 Apr 2022 15:11:01 -0600 (39 minutes, 22 seconds ago), Maxime Devos <maximedevos@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.
[-- Attachment #1: Type: text/plain, Size: 889 bytes --] 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@utah.edu>) (:secure-mail . <slade@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")
Hi,
Benjamin Slade <slade@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