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
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
Looks like this is set for sure.
I even tried running with Java 1.5. I think I might be beyond help, time to
look for a new trade.
Andreas Delmelle-2 wrote:
- Oorspronkelijk bericht -
Van: Surj [mailto:[EMAIL PROTECTED]
Verzonden: vrijdag, juni 13, 2008 09:23 PM
Yes the
Just in case it means something, I ran into this problem when java.awt.headless
was specified as true on the startup configuration for the OAS platform.
Since we were running on a Windows PC we were successfully able to run Batik
(and thereby FOP) by just changing java.awt.headless=false (or
https://issues.apache.org/bugzilla/show_bug.cgi?id=45104
--- Comment #4 from Jeremias Maerki [EMAIL PROTECTED] 2008-07-18 06:28:59
PST ---
Thanks for reporting that, but the problem is limited to 0.20.5. The code
indeed has multi-threading issues:
On Jul 17, 2008, at 20:08, Jeremias Maerki wrote:
I've been quiet about about this PDF extension so far because I didn't
see much harm in doing it in a generic way for some simple name/value
pairs. If that goes much further (like doing hacks to produce some
complex PDF structures but still
