On Sun, Aug 10, 2003 at 09:29:05PM +0300, Beni Cherniavsky wrote: > Keld =?iso-8859-1?Q?J=F8rn?= Simonsen wrote on 2003-08-10: > > > For renderring you just output the fully composed characters. You > > should of cause also output the combining characters but that would > > mean further processing in the renderring engine. Some scripts do > > need this further processing in the renderring engine, such as the > > Indic scripts and Hangul Jamo. > > > Since NFC is merely recommended but not required, it is very possible > for me to have a UTF-8 text file even in simple european languages, > that has decomposed characters. If I want to be able to ``cat file`` > onto the console, it's absolutely required that the console can handle > normalization. If it works in one form but not the other, users are > going to *very* surprised.
My take is that the rendering engine for the console need to be able to display both the fully composed characters, and also the combining characters. The fully composed characters are easy, you just output the bitmaps for the characters. The combining characters are a bit more tricky, and it means that you need more intelligence in the renderring engine. But you need that anyhow for hebrew/arabic and the indic scripts. I thus do not think you need to apply NFC anywhere, you just need to display the characters right. Anyway it would be hard to apply NFC anywhere it is relevant, so it would be better to just apply something in the renderring, IMHO. Best regards keld -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
