Subject: char-ready? is broken for multibyte encodings
From: Mark H Weaver <[email-masked]>
To: [email-masked]
Date: Sat, 28 Jan 2012 05:21:24 -0500
List-Id: <debbugs-submit.debbugs.gnu.org>

The R5RS specifies that if 'char-ready?' returns #t, then the next
'read-char' operation is guaranteed not to hang.  This is not currently
the case for ports using a multibyte encoding.

'char-ready?' currently returns #t whenever at least one _byte_ is
available.  This is not correct in general.  It should return #t only if
there is a complete _character_ available.

     Mark