Andrew Dunbar wrote:
>
> Another thing to keep in mind is whether some iconvs might not
> have support for UCS-2 or UTF-32. But we can always roll our own.
I just came to think of some other possible obstacles: output.
Win32 can only handle up to 16-bit Unicode as output (on the API level), I
don't know if it handles tagged/shifted output >= 2^16. What about the other
supported platforms (X, Photon, BeOS, ...)?
Do TrueType allow chars >= 2^16? Type1?
Stuff like that. Perhaps it wasn't a too bright idea I got after all. :-)
/Mike - please don't cc
