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 FOP otherwise not to generate this tag.
On 12.11.2010 14:15:52 MazZzta wrote: > 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 during transformation if you can get by > without it (and I can get by without it). > > So my question now is: Is it possible to make fop removing that fo:block at > some point before the XSL:FO transformation? Somewhere in the code? or in > the mapping? > > It seems that FOP adds it by default, and that's what I'd like to modify. > > Thanks! > > > On Thu, Nov 11, 2010 at 4:40 PM, Vincent Hennebert > <vhenneb...@gmail.com>wrote: > > > Hi MazZzta, > > > > In the default configuration only fo:block produces a <P> 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 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 my question is about the tagging generated by FOP after the > > > transformation is complete. I open the PDF file with a viewer > > (Particularly > > > Adobe Professional 9) and take a look to the tagging tree. > > > > > > I see something like this: > > > > > > <Document> > > > <Part> > > > <Sect> > > > <P> > > > <L> > > > <H1> > > > <...> > > > ... > > > > > > As you can see, the "main" tagging of the document hangs from a <P> tag > > that > > > is generated always from scratch. Even if I transform a blank document it > > > still builds up this tagging structure, hanging the whole tagging from a > > <P> > > > tag, which in this last case it's empty. > > > > > > Would it be possible to omit that <P> tag and make the whole structure to > > > hang from the <Sect> tag? Like: > > > > > > <Document> > > > <Part> > > > <Sect> > > > <L> > > > <H1> > > > <...> > > > ... > > > > > > I've tried different ideas via XSL, yet I can't get rid of this > > 'annoying' > > > <P> tag. :D > > > > > > Just wondering if someone else has this problem and could help me out. > > > > > > Thanks a lot, > > > > > > MazZzta > > > > > Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
