Re: string encoding by Simon Cozens- February 16, 2001 On Fri, Feb 16, 2001 at 01:20:26PM -0800, Hong Zhang wrote:> 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 beingcompared at the C level, you have far bigger design problems than the choice of UTF.-- A year spent in artificial intelligence is enough to make one believe in God.http://www.nntp.perl.org/group/perl.perl6.internals.unicode/2001/02/msg18.html Re: string encoding by Hong Zhang- February 16, 2001 > > 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-32strings on little endian machines, even both strings are usingthe same...http://www.nntp.perl.org/group/perl.perl6.internals.unicode/2001/02/msg19.html Re: string encoding by Simon Cozens- February 16, 2001 Moved to -unicode, because that&39;s what it&39;s for.On Fri, Feb 16, 2001 at 01:17:03PM -0800, Hong Zhang wrote:> > substr&39;s already been mentioned.> > I have already given the counter argument. The codepoint position is useless> in many cases. They should be deprecated.Uh That doesn&39;t make sense. Codepoint position is exactly what peopleexpect when they use substr. When I say $a = substr($b,10);I want the 10th character. If I get the 10th byte, and we&39;re using...http://www.nntp.perl.org/group/perl.perl6.internals.unicode/2001/02/msg16.html |