Andreas L Delmelle wrote:
>
> Unfortunately, not by using the FOP anttask directly, but some users
> have reported that they use Ant's java task in that case.
>
Hi Andreas,
Actually, the developer who updated the build files to upgrade from fop
0.20.5 to 0.93 changed how Fop was run from ru
http://xmlgraphics.apache.org/fop/0.93/anttask.html doesn't specify any way
that Fop can be assigned more memory. Is there anyway to pass in Xms/Xms
arguments?
Thanks,
P.
--
View this message in context:
http://www.nabble.com/Fop-0.93---Ant-task%3A-Assigning-more-memory--tf3278611.html#a91179
I've upgraded our doc build process from 0.25 to 0.93. In PDF output with
0.25, a table could span multiple pages, with the table header appearing on
each page.
However, with 0.93, the table stops on one page; subsequent rows aren't
printed. Also, the bottom of the table is corrupted. Just two
Jelka wrote:
If you are any good at Java programming .. you can try do it (maybe we
could team together to work on this, mind I am not
a very experienced Java programmer)
Hi Jelka,
I'm afraid I got into technical writing to get away from programming. :) My
Java knowledge is just enough to wr
Is there any way to configure FOP to halt if a graphic is missing, rather
than continue and produce a PDF?
Thanks,
-pm
http://oceanclub.blogspot.com
"Garth Marenghi is the most significant artist that I've worked
with and I've worked with Lulu and four other people, so we're
talking crème de
Andreas L Delmelle said:
Does your document contain tables? With explicit keeps?
Hi Andreas
Yes there's tables, and no, no explicit keeps set.
After much experimentation, it was the following line from my DocBook
stylesheet which seems to cause the problem:
0pt
This sets titles to be fl
Our build system:
* DocBook XSL 1.70.1
* Saxon 6.5.5
* FOP 0.20.5
A particular user manual is giving a "No meaningful layout" error.
[ERROR]
file:/home/pmoloney/svn/pplus/docs/manuals/target/fo/care_applications_g
uide/care_applications_guide.fo:88:696 No meaningful layout in block after
many
"J.Pietschmann" <[EMAIL PROTECTED] wrote:
You mean "via DocBook XSLT", don't you?
Sorry yes; to be more explicit, I should have said we create the .fo file
indirectly (by processing DocBook XML files through Saxon), then run the .fo
file through Fop to create the PDF.
With FOP 0.25, if the
You can find the FO file at:
http://pmoloney.googlepages.com/administrator_guide.txt
I can't reproduce the problem, because I don't have the images that
should be included (and the Arial font, but that should be less
problematic). Can you also post the images? Or try to post a sample
document w
Vincent Hennebert <[EMAIL PROTECTED] wrote:
Not sure if those attribute sets apply to the element that is causing
the problem. Can you post a reduced example that is showing your
problems? Not the source xml file, please, just the generated fo file.
Vincent
Thanks for taking the time to answe
Hi all,
We've updated our DocBook->PDF build process from fop 0.25 to 0.92beta,
involving:
* DocBook XSL 1.70.1
* a customised layer
* Saxon 6.5.5
* FOP 0.92beta
In the output, we're getting 2 types of error; a WARNING and SEVERE.
The WARNINGs are of the type:
[fop] WARNING: Line 1 of a
Hi Andreas,
Sorry, that was a typo in my mail. It was the correct option -fn I
used.
I just double-checked by running the command again to make sure.
... what name you *do* get as a result?
Well, for example, if I try it with Letter Gothic Bold, and use the
option:
-fn "LetterGothicBold"
I'm trying to generate a font metrics files for a Type 1 font, Letter
Gothic, and
I'm not getting the expected result.
When I generate font metrics file, using the following command:
java -cp build\fop.jar;lib\avalon-framework-c
vs-20020806.jar;lib\xml-apis.jar;lib\xercesImpl-2.2.1.jar;lib\xala
13 matches
Mail list logo
