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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
