That question would need to be directed at Norm Walsh, the creator of
the titlepage system. Not sure he would remember why. He wrote the
original code when XSL was new.
Bob Stayton
[email protected]
On 4/30/2021 3:25 AM, Tony Graham wrote:
On 29/04/2021 21:10, Bob Stayton wrote:
No, the template system is not set up for nesting titlepage elements.
It uses the element name of each child of t:titlepage-content to
create a match attribute in the generated xsl:template. The system
is designed to allow the user to specify which titlepage elements
should appear, in what order, and with specific properties, without
having to write XSL.
Thanks for the confirmation.
For more complex needs, I have used the t:named-template feature to
call a custom template (see for example the title element for book),
which could process both title and subtitle. Most often, though, I
just write the XSL I need in custom templates "book.titlepage.recto"
and "book.titlepage.verso" to completely override the generated
templates.
I had already figured that would be necessary.
Is there a reason why 'titlepage.xsl' constructs XSLT elements the
long way:
<xsl:element name="xsl:template">
rather than using the namespace alias feature of XSLT 1.0: [1]
<xsl:namespace-alias stylesheet-prefix="axsl" result-prefix="xsl"/>
<xsl:template ...>
<axsl:template>
?
Regards,
Tony Graham.
