|
I wish Plucker supported Unicode! That would solve the whole character encoding issue. At any rate, UTF-8 would be the way to go, since this works well with standard string functions that assume NULL-terminated sequences and, more importantly, does not require a change to the Plucker specification. IIRC, MultiByteToWidechar() does not support UTF-8 under Windows Mobile, so you'd have to write something yourself. Very easy to do, however.
|