From: "Marcin 'Qrczak' Kowalczyk" <[EMAIL PROTECTED]> > Why would UTF-16 be easier for internal processing than UTF-8? > Both are variable-length encodings. > Performance tuning is easier with UTF-16. You can optimize for BMP characters, knowing that surrogate pairs are sufficiently uncommon that it's OK for them take a bail-out slow path. Andy Heninger IBM, Cupertino, CA [EMAIL PROTECTED]
- Re: 3rd-party cross-platform UTF-8 support Markus Scherer
- Re: 3rd-party cross-platform UTF-8 support Yung-Fong Tang
- Re: 3rd-party cross-platform UTF-8 support David Starner
- Re: 3rd-party cross-platform UTF-8 support Yung-Fong Tang
- Re: 3rd-party cross-platform UTF-8 support Markus Scherer
- RE: 3rd-party cross-platform UTF-8 support Yves Arrouye
- Re: 3rd-party cross-platform UTF-8 support Marcin 'Qrczak' Kowalczyk
- Re: 3rd-party cross-platform UTF-8 support Michael \(michka\) Kaplan
- Re: 3rd-party cross-platform UTF-8 support Andy Heninger
- Re: 3rd-party cross-platform UTF-8 support Andy Heninger
- Re: 3rd-party cross-platform UTF-8 support Andy Heninger
- Re: 3rd-party cross-platform UTF-8 support Andy Heninger
- Re: 3rd-party cross-platform UTF-8 support Tom Emerson
- RE: 3rd-party cross-platform UTF-8 support Carl W. Brown
- RE: 3rd-party cross-platform UTF-8 support Tom Emerson
- Re: 3rd-party cross-platform UTF-8 support Michael \(michka\) Kaplan
- Re: 3rd-party cross-platform UTF-8 support Tom Emerson