Marc Nieper-Wißkirchen scripsit:

> Why only the corresponding procedures for the utf8 and utf16 encoding? For
> example, in case the implementation has a preferred endianess for multibyte
> encoding, it makes sense to provide text->utf32 to output the text encoded
> with that endianess.

UTF-32 is in practice used only internally to a program.  UTF-16 is pretty
much only for text files on Windows, and UTF-8 is used for essentially
all external purposes (about 88% of the Web is UTF-8 or pure ASCII now,
and most of the rest is Latin-1).

--
John Cowan          http://www.ccil.org/~cowan        xxxxxx@ccil.org
Any sufficiently-complicated C or Fortran program contains an ad-hoc,
informally-specified bug-ridden slow implementation of half of Common Lisp.
        --Greenspun's Tenth Rule of Programming (rules 1-9 are unknown)