Michal Jastak wrote:
I've tested Content-Type set by resin and jboss + tomcat, both sets: text/plain
for truetype font and for XML font metrics,
Hmm, standard fallback behaviour. The problem with text/plain is
that some software in the processing chain (server or client) may
be tempted to fiddle with line endings, which is bad for TTF which
are binaries.
I've also tested using application under jboss + tomcat with fonts served
by resin, doesn't work too,
I think the problem may be related only to jboss + tomcat + fop situation,
any suggestions what may cause it ?
Complex software systems have...interesting problems.
I'd first try to download a TTF via HTTP using wget and compare to
the original file in order to check whether the server mangles it
by default. Also try do define application/octet-stream for TTF
in the server configuration and see whether this helps. Then hack
into the FOP font loader and tee the font to a file for comparision
with the original. Finally, did you try to generate a PDF with
jboss+tomcat without font embedding? Something might corrupt
the PDF independently of that. I never had problems with Tomcat
and all kinds of FOP servlets, I never used JBoss though.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
