Hi Max,

The problem with AFP is that there is no concept of a default set of base fonts. You have to purchase your fonts as a pack from IBM and I'm not too sure about the availability of Symbol and Zapfdingbats - they seem have their own way of doing things :).

FOP does however provide a default base font configuration for AFP of sans-serif, serif and monospace - but there are no guarantees as to their availability on any given installation. The branch I am working (http://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_AFPGOCAResources) also contains a populated fop.xconf which provides commonly used raster font configurations for Times Roman, Helvetica and Courier.


Max Berger wrote:

for the same reason I must disagree with the this change: If the fonts
are not available (symbol, zapf dingbats), fop will just fall back to
the default font, where the character is also not available. What you
loose in this case is a little bit of performance. What you gain is the
chance that fop is finally able to produce special characters (which has
been a missing feature for a long time). So rather than shorting this
list, you could enlengthen it with the "symbol" fonts available in afp.


Andreas Delmelle schrieb:
On Jul 17, 2008, at 19:39, [EMAIL PROTECTED] wrote:

Hi Adrian,

Author: acumiskey
Date: Thu Jul 17 10:39:14 2008
New Revision: 677648

URL: http://svn.apache.org/viewvc?rev=677648&view=rev
ZapfDingbats and Symbol is not always available on the AFPRenderer so
we can't have these as default font family properties unfortunately.
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 (?)

Just my 2 cents.


Reply via email to