Quoting Andrew Dunbar <[EMAIL PROTECTED]>:
> I tried to use the new UT_UCS2String class today.
> The operator+=(char) method was causing corrupt results.
> Sometimes my chars were being appended but with garbage in
> the high byte. Other times the entire string seemed to
> get stomped.
>
> Also the size() method is now ambiguous. Does it return the
> number of characters or the number of bytes? Shouldn't we
> have two non-ambiguous methods in both the UT_String and
> UT_UCS2String?
Sorry, please fix these. I committed them quickly and prematurely because I
won't have access to a working computer for another week or so and:
1) wanted this in cvs for revision control & in case anything happened to my hd
2) for other people to work on it :-)
My commit message said that it was largely untested, so please fix this up :-)
Dom
