Hi All,

Has anyone looked at the font state stuff.
It appears we could make some changes to improve the way fonts are

- handle font information easily
- handle font lists, resolving on a char basis
- reduce number of FontState objects if information is the same (or
- allow for serialization as part of area tree

Do we need the FontInfo and FontMetric inside the FontState?
Can we have a list of all font states so that it can be retrieved when
needed for a particular layout of area?

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

Reply via email to