Bill Carpeter wrote: > So, in a pure Unicode environment, for example, an app wouldn't use > different Unicode character values depending on context? They would > use a single, consistent Unicode character value, and then the > rendering engine would select (based on context) which of several > possible Unicode glyphs to display? > > In other words, these rendering differences being discussed are > treated in a fundamentally different way from, say, case shifts? Yes, exactly. It just happens in the case of Arabic that the contextual glyph presentation forms *do* have Unicode code points of their own. But that's not necessarily so for other languages (south Asian ones for instance.) In the case of Arabic it's because of some compatibility considerations, I believe. Lukas
- Interfaces [was: On rendering (Re: Pango will be a probl... Mike Nordell
- Re: Interfaces [was: On rendering (Re: Pango will b... Leonard Rosenthol
- On rendering and reworking the AW backend Tomas Frydrych
- Re: On rendering and reworking the AW backend Mike Nordell
- rendering - how bad is AW font displaying desin... Tomas Frydrych
- Re: rendering - how bad is AW font displaying d... Leonard Rosenthol
- Re: rendering Tomas Frydrych
- Re: rendering - how bad is AW font displaying d... Mike Nordell
- Re: rendering - how bad is AW font displaying d... Leonard Rosenthol
- Re: rendering - how bad is AW font displaying d... WJCarpenter
- Re: rendering - how bad is AW font displaying d... Lukas Pietsch
- Re: rendering - how bad is AW font displaying d... Leonard Rosenthol
- Re: rendering Tomas Frydrych
- Re: rendering Kevin Vajk
- Re: rendering Tomas Frydrych
