[R6RS] proposed conversions between strings and bytevectors

[Michael Sperber]

William D Clinger <will at ccs.neu.edu> writes:

> (utf16->string bytevector)                             procedure
> (utf16->string bytevector endianness)                  procedure
>
> If no endianness is specified, the bytevector must contain the
> representation of a string according to the UTF-16 encoding
> scheme (which permits but does not require a byte order mark).

I don't understand this sentence.  It sounds as though the procedure
might pay attention to the BOM.  However, the reference implementation
seems to assume UTF-16BE, which would be consistent with
`string->utf16'.  I'm going with UTF-16BE.  If anybody objects, yell.

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla