Richard Damon, on Monday, November 11, 2019 12:50 PM, wrote... > Writing 20 UTF-32 characters may ALSO print less than 20 glyphs to the > screen.
This is not true, if the string has more or at least 20 UTF32 characters, and you request 20 character while still talking UTF32, it will print 20. Once you move to UTF16 or UTF8, then, yes, you are correct. > One quick way to see this is that there is a need for NFD and NFC > representations, because some characters can be decomposed from a > combined character into a base character + a combining character, so a > string in NFD form may naturally 'compress' itself when being printed. This is the reason why you want to use UTF32. UTF8, and UTF16 has to use combination of their character set to cover Eastern languages. While all languages fit perfectly in UTF32 and they all have their own unique home. josé _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
