Subject: Re: On rendering and reworking the AW backend
From: Mike Nordell (tamlin@algonet.se)
Date: Sat Jan 06 2001 - 18:27:32 CST
Tomas Frydrych wrote:
> On the other hand, if the
> engine is external to the code that handles the raw text, you
> cannot just ask it, you have to provide it with additional information
> before it can draw. The point I am trying to make is that such an
> information is not readily available in AW at present, and it will
> require substantial work, whether you decide to replace our exising
> block handling mechanism with Pango itself, or to patch a
> rendering engine into it in some other way.
Ouch, I didn't know the AW font displaying design was *that* bad. But I'd
like some more confirmation before I myself make a judgement. If I were only
to believe your points, our font rendering is relly broken and has to be
fixed. Is it this broken?
> All I am concerned with is that the amount of work that integrating
> a rendering engine into AW will take would not be underestimated.
> These issues should have been really thought through before the
> AW backend was designed and I am inclined to think that if we are
> serious about this, we should start dealing with it before any major
> rewrite of the AW back end.
If the problem is indeed on the magnitude you display we have serious
problems. Really serious ones. But, in that case I'm surprised no one have
noticed this earlier.
So, do we *really* have these problems, in case we have real problems and
must fix this, or is it another misunderstanding of something?
On the other hand, perhaps someone *have* displayed these problems before
but people have been too occupied with "other stuff" to notice.
I don't know, and I'd *really* like you to elaborate.
/Mike - please don't cc
This archive was generated by hypermail 2b25 : Sat Jan 06 2001 - 18:28:14 CST