On Jul 20, 2008, at 17:15, J.Pietschmann wrote:
Andreas Delmelle wrote:
I understand... I still think it's a nice showcase for
character-by-character font-selection added by Max, so I'm
wondering, if
the AFPRenderer is the only exception, we should be looking at a
way to
fall back with a warning, rather than disabling the feature for all
other output formats as well (?)
I think we could ask the renderer about available fonts. How should
the
API look like?
I haven't really thought this through yet, so I guess, from my
perspective, anything goes, as long as it would disable the feature
only for those renderers not supporting it.
If I'd have to implement it, I'd be looking at overriding
fo.properties.FontFamilyPropertyMaker.make(PropertyList), which has
access to the FOUserAgent, or the FopFactory's FontManager, and
should thus be able check for the availability of the fonts to find
out which ones can be used as initial values. That would be a more
than viable alternative for the hardcoded default in FOPropertyMapping.
But it's all still a bit vague...
Andreas
