From: Andy Wingo <wingo@pobox.com>
To: Josep Portella Florit <jpf@primfilat.com>
Cc: 22667-done@debbugs.gnu.org
Subject: bug#22667: string->bytevector encoding error
Date: Sun, 07 Aug 2016 23:25:29 +0200 [thread overview]
Message-ID: <87y448nueu.fsf@pobox.com> (raw)
In-Reply-To: <87lh1zg7ye.fsf@pobox.com> (Andy Wingo's message of "Mon, 20 Jun 2016 18:07:21 +0200")
Hi,
On Mon 20 Jun 2016 18:07, Andy Wingo <wingo@pobox.com> writes:
> On Sun 14 Feb 2016 23:18, Josep Portella Florit <jpf@primfilat.com> writes:
>
>> (use-modules (ice-9 iconv))
>> ;; These expressions throw 'encoding-error':
>> (string->bytevector (make-string 129 #\A) "UTF-16")
>> (string->bytevector (make-string 65 #\A) "UTF-32")
>
> For what it's worth, this appears to be fixed in 2.1.3. However we
> should fix 2.0 as well.
Fixed. Thanks for the report, and thanks to Mark for diagnosing the
problem.
Andy.
prev parent reply other threads:[~2016-08-07 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 22:18 bug#22667: string->bytevector encoding error Josep Portella Florit
2016-03-03 17:55 ` Mark H Weaver
2016-06-20 16:07 ` Andy Wingo
2016-08-07 21:25 ` Andy Wingo [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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y448nueu.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=22667-done@debbugs.gnu.org \
--cc=jpf@primfilat.com \
/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).