This email is autogenerated from the output from:
http://jakarta.apache.org/builds/gump/2001-08-19/xml-fop.html
Build results exceed maximum length.Please see URL above for details.
My application which used FOP by fiering SAX event on it stopped working
when I updated from FOP 0.19 to FOP 0.20.
I used the following code for FOP 0.19:
Driver driver = new Driver();
driver.setRenderer(org.apache.fop.render.pdf.PDFRenderer,
Thanks for these suggestions,. I think I've narrowed down the problem to
font-embedding.
If I use Helvetica in my xsl:fo, then I can export to rtf without problems,
but using the Arial metrics files I created and embedding these results in
garbled rtf output. Viewing the Document properties in
Hello Struan,
It looks as though you must have changed addLine as well to add the
border-style, since that isn't in the current version (at least not the
one I got from CVS last night.)
I'm the one responsible for changing this code in doFrame because when
borders are drawn using lines in PDF,
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
Here's the problem in a nutshell: Java's Font class knows about the True Type fonts
that it loaded from jre\lib
\fonts and it also seems to know about TrueType fonts that are in the operating
system's directory of fonts (on
my NT4 box they are in winnt\fonts). But those font names are not
Hi Eric,
Sorry if no one has answered your plea before now.
Unfortunately (or perhaps fortunately?) I don't have any problem with
the example you sent. I'm using the latest CVS, but if you are using an
earlier version of FOP, you probably should try with the latest release
which is 0.20.1.
I've
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
Hi fop and xalan dev,
The problem here seems to be that the XSLT document function, when
called with a single argument which is a node-set (in the fop case, a
single element or attribute node) is now using the current directory as
the base URI to resolve relative URI references.
It should use
Struan,
Oops, I hadn't noticed the second version of addLine taking the
ruleStyle since it wasn't being called in the doFrame stuff when I made
my change. Duhh.
The baseline alignment stuff is harder than the straight after align.
Our line-height calculations need to be right before we get into
From: Arved Sandstrom [mailto:[EMAIL PROTECTED]]
'space-before' is _not_ inheritable in any case, so it is
something of a
moot point. What you are confusing that with is the
possibility of using the
inherit keyword, which is a different beast.
Hi Arved,
Thank you for clearing that up
What's new?
===
This release adds few improvements to the previous release:
- the ability to process the result of an XSLT transformation through
the Apache FOP processor.
- initial integration with the DocBook-XSL project; HTML and PDF
generation and viewing from within Emacs of
12 matches
Mail list logo
