4 Nov
2004
4 Nov
'04
8:25 p.m.
And from the RFC: "In the UTF-16 encoding, characters are represented using either one or two unsigned 16-bit integers, depending on the character value." (http://www.ietf.org/rfc/rfc2781.txt)
As I said, UTF-16 implies 16-bit wide characters, hence, 16-bit wide strings in Pike, which clearly explains why I use this term.
Read again, UTF-16 implies 16-bit integers where the characters are build from one *or two* integers.
utf8_to_string does not unpack to UTF-16; values that doesn't fit inside 16 bits are not stored in two integers; they are stored in one integer.