Re: [docbook-apps] Possible <Glossary>/<Subtitle> bug?

["Bob Stayton" <bobs@sagehill.net>]

Sorry, I got the mode name wrong.  It should be
glossary.titlepage.recto.mode and not
glossary.recto.titlepage.mode.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: <martin.gautier@myrnham.co.uk>
To: "Bob Stayton" <bobs@sagehill.net>
Cc: <docbook-apps@lists.oasis-open.org>
Sent: Thursday, February 12, 2004 4:26 PM
Subject: Re: [docbook-apps] Possible <Glossary>/<Subtitle> bug?


> Bob
>
> >>I'll see about removing the obsolete code.
> That would be handy ;o)
>
> >>In fact, the glossary subtitle is being handled by the default template
> for subtitle in mode='titlepage.mode'.
> OK. I can see that happening.
>
> >> If you want something different for a glossary subtitle, you can add a
> template [like this] to your customization layer:
> Ah. Now I have a problem.
>
> My customisation layer now has:
>
> ...
> <xsl:include href="my.titlepage.templates.xsl"/>
> ...
> <xsl:template match="title" mode="glossary.recto.titlepage.mode">
>   <h2 class="myglossarytitle"><xsl:apply-templates
> mode="titlepage.mode"/></h2>
> </xsl:template>
>
> <xsl:template match="subtitle" mode="glossary.recto.titlepage.mode">
>   <h3 class="myglossarysubtitle"><xsl:apply-templates
> mode="titlepage.mode"/></h3>
> </xsl:template>
>
> Where my Titlepage mechanism consists of my.titlepage.templates.xml:
>
> <t:titlepage t:element="glossary" t:wrapper="div" class="titlepage">
>   <t:titlepage-content t:side="recto">
>     <title t:force="1" t:named-template="component.title"
> param:node="ancestor-or-self::glossary[1]"/>
>     <subtitle/>
>   </t:titlepage-content>
>
> which compiles without error into my.titlepage.templates.xsl.
>
> <xsl:template match="title"... is outputing correctly but <xsl:template
> match="subtitle"... is still being skipped and so falls back to the
> default <xsl:template match="subtitle" mode="titlepage.mode"> template.
>
> Is there anything I need to add to my.titlepage.templates.xml get my
> customisation to kick in? Previously I've managed to make my <book>
> titlepage work correctly in this manner so I'm familiar which the concept.
> I must have missed something somewhere though...
>
> Mart
>
>
>