From: dd <dur...@gm...> - 2014-11-04 11:28:23
|
Many thanks Markus. DD On Tue, Nov 4, 2014 at 9:57 AM, Markus Scherer <mar...@gm...> wrote: > Welcome to internationalization :-) > > On Sun, Nov 2, 2014 at 12:12 AM, dd <dur...@gm...> wrote: > >> Right now, my application doesn't support Unicode string comparisons >> like string has ISO Latin characters. I would like to fulfill this by >> taking help of icu. >> >> Is it right choice? >> > > It's a good an commonly used choice, anyway. > > If you compare strings for showing sorted lists to users, you will need to > use a Collator. See http://userguide.icu-project.org/collation > > If you compare strings for internal processing, you will need > normalization and case-folding, possibly via the combined NFKC_Casefold > form. > > Please take a look at the User Guide and the API references. > > What are the disadvantages with icu? >> > > As with any library, you need to think about integration and packaging. > > ICU might already be built into some of the platforms or frameworks you > are going to support. If they expose the functionality you need, then you > don't need to ship your own copy of ICU there. For example, Android SDK, > iOS, and the JavaScript i18n API in many modern browsers make subsets of > ICU functionality available. > > Best regards, > markus > > > ------------------------------------------------------------------------------ > > _______________________________________________ > icu-support mailing list - icu...@li... > To Un/Subscribe: https://lists.sourceforge.net/lists/listinfo/icu-support > Archives/Project Info: http://site.icu-project.org/contacts > > |