From: Arun Isaac <arunisaac@systemreboot.net>
To: Christopher Baines <mail@cbaines.net>, guile-email@systemreboot.net
Subject: Re: [guile-email] more decoding errors
Date: Sat, 28 Sep 2019 13:42:32 +0530 [thread overview]
Message-ID: <cu7o8z4kff3.fsf@systemreboot.net> (raw)
Message-ID: <20190928081232.6I_WqVbVDVq3p5yuptbewdx8yrZQpggD-T4xQuDmFm0@z> (raw)
In-Reply-To: <874l0xquvx.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
Hi,
Thanks for the bug report!
> From: =?UTF-8?Q?Ludovic_Court=E8s?= <ludo@gnu.org>
This MIME encoded word is incorrectly encoded. UTF-8 is declared as the
encoding, while actually ISO-8859-1 has been used.
> I'm still not exactly sure why, some experimenting shows that the
> following decodes to what I guess is the intended text:
>
> Ludovic_Court=C3=A8s
Yes, this is the correct encoding.
> Similarly to the recent changes, specifying 'substitute as the third
> argument to bytevector->string at least avoids crashing in this case.
Indeed, the substitute conversion strategy is the only correct way to
proceed. I've made this change and pushed to master.
https://git.systemreboot.net/guile-email/commit/?id=9d82904011516530b6ef1bcd53cef220db485e7a
I'm ok with having another bugfix release, but I think we should wait a
week or two in case more bugs are found. WDYT?
Regards,
Arun.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-09-28 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 21:41 Christopher Baines
2019-09-28 8:12 ` Arun Isaac [this message]
2019-09-28 8:12 ` Arun Isaac
2019-09-28 9:34 ` Christopher Baines
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7o8z4kff3.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guile-email@systemreboot.net \
--cc=mail@cbaines.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox