From: Tomas Volf <~@wolfsden.cz>
To: 69381@debbugs.gnu.org
Subject: bug#69381: mumi does not correctly display (some?) non-ascii characters
Date: Sun, 25 Feb 2024 14:04:10 +0100 [thread overview]
Message-ID: <Zds6yhPkZ0Id6SAT@ws> (raw)
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
Hi,
when I compare mumi page[0] with debbugs page[1], the from field displays "???"
in mumi, but "宋文武" in debbugs.
Have a nice day,
Tomas Volf
0: https://issues.guix.gnu.org/57268
1: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57268
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-02-25 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 13:04 Tomas Volf [this message]
2024-05-14 23:12 ` bug#69381: [PATCH] Convert HTML to UTF-8 ourselves. (Closes: #69381) Felix Lechner via Bug-mumi via Bug reports for GNU Guix Mumi.
2024-11-02 0:07 ` bug#69381: [PATCH] web: Use string to avoid losing unicode characters noe--- via Bug-mumi via Bug reports for GNU Guix Mumi.
2024-11-02 0:14 ` Noé Lopez via Bug-mumi via Bug reports for GNU Guix Mumi.
2024-11-02 2:23 ` Noé Lopez via Bug-mumi via Bug reports for GNU Guix Mumi.
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://issues.guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zds6yhPkZ0Id6SAT@ws \
--to=~@wolfsden.cz \
--cc=69381@debbugs.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).