I now think that this may not work out at all. It looks like if we want proper

Unicode handling we'll need to implement a series of codecs and converters as
well as tables of codepages and lookups.  It'll be interesting, I guess, but
it makes me care a lot less about proper encoding.  Anyway, UtfString uses
shorts instead of chars, so it's a step in the right direction, but still not
enough to be able to handle proper UTF-16 encoding, maybe UCS-2 encoding, but...
...that's lame.  Bu::FBasicString has been generalized a bit with optimizations
from libc for char based strings.  It also, unfortunately, still uses char-only
functions in several places, those all rely on char casting strings at the
moment just to get the thing to compile.  Basically, it's not a good UTF-16
solution yet, and it may never be and remain compatible with char based strings.

0 files changed, 0 insertions, 0 deletions