>> The notion behind rendering is that only a single code is used to >> represent/store/input the character, but the rendering engine takes >> care of displaying the correct glyph based on the immediate >> context. 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? -- [EMAIL PROTECTED] (WJCarpenter) PGP 0x91865119 38 95 1B 69 C9 C6 3D 25 73 46 32 04 69 D6 ED F3
- Re: On rendering (Re: Pango will be a problem) Leonard Rosenthol
- 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
