Hi again,
That's it, you were right. The bug resided within my XSL file and I finally
found and removed it.
Now I get it going swimmingly.
Dual thanks to both of you.
MazZzta
On Fri, Nov 12, 2010 at 2:36 PM, Jeremias Maerki wrote:
> Hi MazZzta,
> FOP does not add the "P" by itself. As Vincent
Hi MazZzta,
FOP does not add the "P" by itself. As Vincent said: you have an
fo:block right under fo:flow and the other elements inside that. If you
want it to go away, you have to change your XSLT so it doesn't produce
that fo:block as the parent for all other FO elements. There's no way to
tell F
Hi Vincent, thanks for your quick reply.
I am aware that deleting the fo:block element in the FO file may do the
job.
However I'd prefer not editing the FO file unless it is absolutely
necessary, as it is said in the Apache FOP documentation online, which
encourages not to produce a FO file durin
Hi MazZzta,
In the default configuration only fo:block produces a tag. So in
your FO file you must have an fo:block element as the first child of the
fo:flow, surrounding the rest of the content. Just remove it and that
should do.
HTH,
Vincent
On 10/11/10 16:23, MazZzta wrote:
> (Using FOP Tr
(Using FOP Trunk)
Hi all,
I'm working with FOP embedded in a Java application to generate PDF files
with accessibility features enabled.
I've set everything up an it works pretty well. Further, I've customized
the mapping so that I can map whatever structure tag I need (H1, H2... etc).
However
