xmlgraphics-fop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Xmlgraphics-fop Wiki] Update of "FontSelectionStrategy" by AndreasDelmelle
Date Sun, 08 Jul 2007 07:36:18 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" for change notification.

The following page has been changed by AndreasDelmelle:

  The FOTexts' characters are already looped over many times, so it does not really matter
''where'' in the process the check for the presence of a glyph in the current font is inserted.
The only thing that would really need to change is the point where the fonts are first loaded:
much sooner than is the case with the current implementation, but only from the point of view
of a ''single'' FOP run. The argument here is that this matters very little in ''multi-session''
contexts where the fonts are handled by the !FopFactory, and as such already loaded in 90%
of the cases.
+ After looking a bit deeper, there seems to be a more fundamental problem in {{{CommonFont.getFontState()}}}:
the method checks for {{{fontState == null}}} and if so, sets it to an instance of {{{Font}}}
corresponding to the triplet using the first font-family in the list that is supported (see
what {{{FontInfo.fontLookup(String[],String,int)}}} does). All subsequent times this method
is called, the very same {{{Font}}} instance is returned. 
+ Through {{{FontInfo}}} one can create a new instance corresponding to a different triplet,
by explicitly getting the next font-family through something like {{{CommonFont.getFontFamily()[x]}}}?
This seems suboptimal somehow...

To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org

View raw message