Re: Using libunistring for string comparisons et al

[Mike Gran]

> The reason I am still arguing this point is because I have looked
> seriously at what I would need to do to (A) fix our i18n problems and
> (B) make the code efficient.  I very much want to fix these things,
> but the pain of trying to do this with our current scheme is too much
> for me to bear.  I shouldn't have to rewrite libunistring, and I
> shouldn't have to write 3 or 4 different variants of each procedure
> that takes two string parameters.

What procedures are giving incorrect results?

Thanks,

Mike