From: "Noé Lopez via Bug-mumi via Bug reports for GNU Guix Mumi." <bug-mumi@gnu.org>
To: 69381@debbugs.gnu.org
Subject: bug#69381: [PATCH] web: Use string to avoid losing unicode characters.
Date: Sat, 02 Nov 2024 03:23:24 +0100 [thread overview]
Message-ID: <87froape5f.fsf@xn--no-cja.eu> (raw)
In-Reply-To: <Zds6yhPkZ0Id6SAT@ws>
Small update,
I’ve investigated the issue in fibers and I now blame the guile web
library for the issue. Apparently it sets the port to ISO-8859-1
encoding each time you call read-request, but it acts like « yeah don’t
worry just use utf-8 for your body » in the docs.
That’s fine UNLESS you use chunked transfers (omitting content-length in
fibers), in which case it just decides to blow up :///// (it assumes one
character = one byte)
In the end I’m pretty sure any of this could have been avoided by just
not replacing every character with question marks. Had it kept the
invalid bytes intact they would have translated back with no issue.
prev parent reply other threads:[~2024-11-02 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 13:04 bug#69381: mumi does not correctly display (some?) non-ascii characters Tomas Volf
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. [this message]
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=87froape5f.fsf@xn--no-cja.eu \
--to=bug-mumi@gnu.org \
--cc=69381@debbugs.gnu.org \
--cc=noe@xn--no-cja.eu \
/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).