Adrian, 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.
Max 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 >> Log: >> 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. > > Andreas
signature.asc
Description: OpenPGP digital signature