unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Benjamin Slade <slade@lambda-y.net>, 55158@debbugs.gnu.org
Subject: bug#55158: bug: mu/mu4e on Guix does not use correct encoding/utf-8
Date: Sat, 30 Apr 2022 23:11:01 +0200	[thread overview]
Message-ID: <8f6446223491c1899efdab3a8cb79abcc151ef21.camel@telenet.be> (raw)
In-Reply-To: <87o80mvyq5.fsf@lambda-y.net>

[-- 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 --]

  reply	other threads:[~2022-04-30 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  0:22 bug#55158: bug: mu/mu4e on Guix does not use correct encoding/utf-8 Benjamin Slade
2022-04-30 21:11 ` Maxime Devos [this message]
2022-04-30 21:50   ` Benjamin Slade
2022-05-07 20:23     ` Benjamin Slade
2022-06-08 21:32       ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=8f6446223491c1899efdab3a8cb79abcc151ef21.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55158@debbugs.gnu.org \
    --cc=slade@lambda-y.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).