You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Will Gilbert <gi...@informagen.com> on 2003/12/16 16:27:58 UTC
Section Title in Page Footer
I would like to put a current section name is the footer of the PDF.
I've used the footer to successfully write the page number and date and
other static information.
This would be written into <fo:static-content
flow-name="xsl-region-after">. I am afraid that the words
"static-content" might just say it all and I can't do this.
I played around with some XPATH notations and got a few things to print
but I could figure what the current node/context is when this region is
processed.
FAQ, links, sample code welcome.
--will
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: Section Title in Page Footer
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Will Gilbert wrote:
> Thanks, Chris. I got this to work as advertised, used Google to get the
> exact syntax correct. A question -- Why does a fo:marker have to be the
> first child of a fo:flow?
A fo:marker must be the first child of the parent FO, which is
not necessarily a fo:flow. You can attach a marker to basically
every FO which may be a descendant of a fo:flow, with the
restriction that a marker must not be a descendant of another
marker.
> Or is this a design compromise for 0.20.5 in lieu of the re-factored
> development branch?
I'm not aware that there is such a restriction in FOP. Perhaps
you got an error message because you had whitesp[ece before a marker
in a mixed content context, like
<fo:block>
<fo:marker> ...</fo:marker>
foo...
The spec explicitely forbids this, check
http://www.w3.org/TR/xsl/xslfo/slice6.html#fo_marker
You have to write
<fo:block><fo:marker> ...</fo:marker>
... foo ...
in this case
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: Section Title in Page Footer
Posted by Will Gilbert <gi...@informagen.com>.
On Dec 16, 2003, at 11:45 AM, Chris Bowditch wrote:
> Will Gilbert wrote:
>> This would be written into <fo:static-content
>> flow-name="xsl-region-after">. I am afraid that the words
>> "static-content" might just say it all and I can't do this.
>
> fo:marker and fo:retrieve-marker can be used to put variable content
> into the static regions.
>
> <snip/>
>
>> FAQ, links, sample code welcome.
>
> in the FOP distribution examples/fo/markers sub directory there is an
> example that shows how to use markers.
>
> Chris
Thanks, Chris. I got this to work as advertised, used Google to get
the exact syntax correct. A question -- Why does a fo:marker have to
be the first child of a fo:flow?
I was able rewrite my fo structure to accommodate this requirement but
many of the examples returned by Google showed fo:marker's within
fo:blocks. It seems odd to force each section be within its own
seperate fo:flow.
Or is this a design compromise for 0.20.5 in lieu of the re-factored
development branch?
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org
Re: Section Title in Page Footer
Posted by Chris Bowditch <bo...@hotmail>.
Will Gilbert wrote:
> This would be written into <fo:static-content
> flow-name="xsl-region-after">. I am afraid that the words
> "static-content" might just say it all and I can't do this.
fo:marker and fo:retrieve-marker can be used to put variable content
into the static regions.
<snip/>
>
> FAQ, links, sample code welcome.
>
in the FOP distribution examples/fo/markers sub directory there is an
example that shows how to use markers.
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org