On Wed, 2002-10-23 at 21:41, Victor Mote wrote:
Keiron Liddle wrote (a long time ago, July 18 to be exact):
Has anyone looked at the font state stuff.
It appears we could make some changes to improve the way fonts are
handled.
- handle font information easily
- handle font lists,
Keiron Liddle wrote (a long time ago, July 18 to be exact):
Has anyone looked at the font state stuff.
It appears we could make some changes to improve the way fonts are
handled.
- handle font information easily
- handle font lists, resolving on a char basis
- reduce number of FontState
Keiron Liddle wrote:
Can we have a list of all font states so that it can be retrieved when
needed for a particular layout of area?
This is exactly what I'm currently thinking about. This
allies to all property bundles. There are only so much
different font states really used in a specific
Hi Victor,
I think that Jeremias covered most of your questions.
This is a related issue to handling the font state.
For embedded fonts it needs to create a font metrics and (at least in
the case of pdf) enable the font to be embedded.
So find out what font metrics are needed by FOP then the
Hi Keiron
Not enough to be of any help right now. But reading this the Flyweight
pattern from the Design Patterns book comes to my mind immediately. The
list of all font states is the consequence of this pattern which could
be very helpful for the renderers. The PS renderer still writes a list
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
On Thu, 2002-07-18 at 16:05, Oleg Tkachenko wrote:
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.
Normally it does a lookup on every char anyway.
I would have to check but
