Keiron Liddle wrote:

> - handle font lists, resolving on a char basis
Do we really need it? It'll slow down rendering. btw, neither xep nor antenna 
don't support it.

> - reduce number of FontState objects if information is the same (or
> similar?)
That's good idea, now we create new FontState for each text node. What about 
FontState pool?

> - allow for serialization as part of area tree
> Do we need the FontInfo and FontMetric inside the FontState?
Not sure about FontMetric but FontInfo object is actually 1 for the whole 
rendering process and each FontState doesn't have to remember it.

Oleg Tkachenko
Multiconn International, Israel

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to