GNU bug report logs - #69381
mumi does not correctly display (some?) non-ascii characters

Previous Next

Package: mumi;

Reported by: Tomas Volf <~@wolfsden.cz>

Date: Sun, 25 Feb 2024 13:27:03 UTC

Severity: normal

Tags: patch

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Noé Lopez <noe <at> xn--no-cja.eu>
To: 69381 <at> debbugs.gnu.org
Subject: bug#69381: [PATCH] web: Use string to avoid losing unicode characters.
Date: Sat, 02 Nov 2024 03:23:24 +0100
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.




This bug report was last modified 101 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.