[EMAIL PROTECTED] wrote:
Then... use Unicode internally in your software.... regardless you use UTF-8 or UCS2 as the data type in the interface, eventually some code need to convert it to UCS2 for most of the processing. Unless you use UCS2 internally, you need to pay for the performance, either inside the library our in your own code.
For cross-platform software (NT,Solaris,HP,AIX), the only 3rd-party unicode support
I found so far is IBM ICU.
It's a very good support for cross-platform software internationalization. However,
ICU internally uses UTF-16, For our application using UTF-8 as input and output,
I have to convert from UTF-8 to UTF-16, before calling ICU functions (such as ucol_strcoll() )I'm worried about the performance overhead of this conversion.
Are there any other cross-platform 3rd party unicode supports with better UTF-8 handling ?
Thanks a lot.-Changjian Sun