Got them. Thanks for that.
Unfortunately I run into 'a next' problem.
SEVERE: Exception stack tracejava.lang.IndexOutOfBoundsException: Index: 3,
Size: 2
at java.util.ArrayList.RangeCheck(ArrayList.java:546)
at java.util.ArrayList.get(ArrayList.java:321)
at
Just yesterday I got fop 0.95 installed to try tp make a pdf version
of the GnuCash (www.gnucash.org) guide, and the resukts look great for
the first time. Obviously some tinkering will need to be done, but
that is to be expected for a newbie to docbook and fop.
I got a slew of warnings, most
Please ignore last stack trace / problem. My mistake. Apologies for the
noise.
Peter
Peter Coppens wrote:
Got them. Thanks for that.
Unfortunately I run into 'a next' problem.
SEVERE: Exception stack tracejava.lang.IndexOutOfBoundsException: Index:
3,
Size: 2
at
First, thanks to the fop developers for a fine program--it has enabled
successful pdf generation of the GnuCash guide which apparently hasn't
been possible for some time with other docbook tool chains.
I am using the trunk version of fop and have a couple of comments:
When I execute 'fop'
Hello,
When referring to a page that is not present in the pdf, the pdf-image
extension throws an exception.
SEVERE: Exception stack tracejava.lang.IndexOutOfBoundsException: Index: 3,
Size: 2
at java.util.ArrayList.RangeCheck(ArrayList.java:546)
at
Hi Tom,
Tom Browder wrote:
Just yesterday I got fop 0.95 installed to try tp make a pdf version
of the GnuCash (www.gnucash.org) guide, and the resukts look great for
the first time.
That’s good news!
Obviously some tinkering will need to be done, but
that is to be expected for a newbie
On Wed, Oct 1, 2008 at 1:11 PM, Vincent Hennebert [EMAIL PROTECTED] wrote:
Hi Tom,
Tom Browder wrote:
...
Is there a way to get fop to point to the source of the warnings?
You have to write the XSL-FO produced by the XSLT processor into a file.
...
For debugging purpose you can proceed in
Tom Browder wrote:
On Wed, Oct 1, 2008 at 1:11 PM, Vincent Hennebert wrote:
Hi Tom,
Tom Browder wrote:
...
Is there a way to get fop to point to the source of the warnings?
You have to write the XSL-FO produced by the XSLT processor into a file.
...
For debugging purpose you can
On Wed, Oct 1, 2008 at 8:28 PM, John Brown [EMAIL PROTECTED] wrote:
One more thing: the XSL-FO produced by FOP does not contain any
new line characters, so FOP will tell you that the error is on line 1 at
position 7458 o something similar. You can format the XSL-FO using
'xmllint --format'
