Re: string encoding

> > But the memcmp() can not be used for UTF-32 string comparison, because
> > of endian issue.
> 
> What endian issue? If you have two differently-endian strings being
> compared at the C level, you have *far* bigger design problems 
> than the choice of UTF.

My argument was:
You can use memcmp() to compare binary order of two UTF-8 strings.
But you can not use memcmp() to compare binary order of two UTF-32
strings on little endian machines, even both strings are using
the same endian.

BTW, with UTF-8, you never worry about endian issue.

Hong