Hi Brad,
Indeed, the template for epigraph is not well set up for extensions, as
it selects specific elements to process:
<xsl:template match="epigraph">
<fo:block>
<xsl:call-template name="anchor"/>
<xsl:apply-templates select="para|simpara|formalpara|literallayout"/>
<xsl:if test="attribution">
<fo:inline>
<xsl:text>—</xsl:text>
<xsl:apply-templates select="attribution"/>
</fo:inline>
</xsl:if>
</fo:block>
</xsl:template>
I think the author did that to handle attribution out of document order.
That first select should probably be:
select="node()[not(local-name(attribution))]"
Bob Stayton
Sagehill Enterprises
[email protected]
On 4/30/2014 7:26 AM, Brad Scott wrote:
Hi
I'm using the DocBook Publishers schema, and we've been customising the
DocBook XSL for the poetry, drama and dialogue element display.
However, I notice that, if any of those elements are within an epigraph,
the output using the standard uncustomised tools strips out the content;
it doesn't just pass it through with the markup escaped in red, it loses
it completely.
Just thought you'd like to know, since this is different behaviour from
when those elements occur in a blockquote, which seems a little odd, and
it took us some time to notice.
Best, and thanks!
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
