On Monday 09 April 2007 21:28:35 Michael Sweet wrote: > OK, first I would recommend going to unicode.org and doing some > background reading on Unicode. Don't concern yourself specifically > with UTF-8, because that is just one possible encoding of Unicode. > > Unicode has four possible "normalization" forms, abbreviated NFC > (Composed), NFKC (Composed but using the ISO-8859-1 compose characters > in preference to any newer character codes), NFD (decomposed), and > NFKD (decomposed except for ISO-8859-1 characters). > > "Composed" means that a single character value is used, for example > an A with ^ on the top (Á in HTML) would be Unicode character > 00C1. > > "Decomposed" means that multiple values are used to compose the final > character. For the previous example, the characters 0301 (^) and > 0041 (A) would be used instead. > > So the issue is not UTF-8 vs. UTF-16 vs. UTF-32, but whether your > locale defines the necessary case mapping tables for the languages > you use and which normalization form you use for your text.
Thank you, I already intend to finish reading book on unicode.org, but don't have time now and I thought that what I've learned about Unicode so far, would be sufficient enough for one operation which I need most right now - "case-insensitive comparation". _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
