I would like to place an anchor as a direct child of a section, so
that when I xi:include the content of the section, I have an anchor
with which to cross-reference the content.
Unfortunately, the stock transformations always convert the anchor to
an inline, regardless the parentage of the anchor.
(A) Is there a reason why I should not be able to insert an anchor as
the child of the section?
(B) Assuming that I should be able to, why on earth is this
customization to the templates not working? I could swear the test
should work; it looks to be analogous to any number of examples in the
transformation code. I is teh dumb, I guess.
<xsl:template match="d:anchor">
<xsl:variable name="id">
<xsl:call-template name="object.id"/>
</xsl:variable>
<xsl:choose>
<xsl:when test="parent::d:section">
<fo:block id="{$id}"/>
</xsl:when>
<xsl:otherwise>
<fo:inline id="{$id}"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
(For benefit of those who might search the mailing list for xi:include/
xinclude examples, I'm using variations on this construct:
<xi:include
href="source.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook)
xmlns(xi=http://www.w3.org/2001/XInclude)
xpointer(//db:secti...@xml:id='section_id']/db:title/following-
sibling::*)"
/>
)
--
David Priest [email protected] [email protected]
Polaris 250.549.2558 x249
Documentation and Informatics Geek.
Django Ponies Wrangler.
CONFIDENTIALITY NOTICE: This electronic mail message and any attachment hereto
may contain confidential information of Meyer Sound Laboratories, Incorporated
and is intended for the personal and confidential use of the designated
recipient(s) only. If you are not the intended recipient (or responsible for
delivering the message to the intended recipient), you have received this
message in error and any review, distribution, or copying of this message or
any attachment hereto is prohibited. If you have received this message in
error, please promptly notify the sender and permanently delete it from your
computer.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]