Arne Götje (高盛華) wrote:
> [..] yes, it depends totally on the font to define the
> *position* of the accents (and weather or not they can be
> stacked). But it depends on the rendering engine to *interpret*
> the information the font gives about the accents.
>
> BTW: there was no irony in my state
This subject sometimes comes up, but not nearly frequently enough
I think.
The web archives of this list at
http://mail.nl.linux.org/linux-utf8/ do not preserve utf-8
characters intact. This is absurd given the subject of this list.
Is there no way of remedying this situation? Could this list be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan Willem Stumpel wrote:
> Arne Götje (高盛華) wrote:
>> [..] yes, it depends totally on the font to define the
>> *position* of the accents (and weather or not they can be
>> stacked). But it depends on the rendering engine to *interpret*
>> the informa
On Mon, Dec 11, 2006 at 11:00:31AM +0100, Jan Willem Stumpel wrote:
> This subject sometimes comes up, but not nearly frequently enough
> I think.
>
> The web archives of this list at
> http://mail.nl.linux.org/linux-utf8/ do not preserve utf-8
> characters intact. This is absurd given the subjec
Arne Götje (高盛華) wrote (in another thread, replying to Rich
Felker):
> In this case, *you* need to *define* which combinations you
> need and *how* they should be displayed.
and (replying to Andries Brouwer):
> But please, if you do so, provide the necessary information
> (which combinations a
On Mon, Dec 11, 2006 at 05:06:23PM +0100, Jan Willem Stumpel wrote:
> I am beginning to think that the responsibility for correct
> "combining accents" behaviour rests primarily with the rendering
> engine, rather than with the fonts. The fonts must, of course,
> include the combining accents, oth
On Mon, Dec 11, 2006 at 05:49:22PM +0100, Andries Brouwer wrote:
> On Mon, Dec 11, 2006 at 05:06:23PM +0100, Jan Willem Stumpel wrote:
>
> > I am beginning to think that the responsibility for correct
> > "combining accents" behaviour rests primarily with the rendering
> > engine, rather than with
> The OpenType system is very poorly designed from what I can tell. In
> the Tibetan fonts I've examined, rather than just saying "character
> U+0F62 needs to use an alternate glyph when followed by any of {list
> here} combining characters", there are individual ligature
> combination tables for e
