This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: [docbook-apps] Re: Contents of CVS $Id$
- From: Diane Larin <diane at inro dot ca>
- To: docbook-apps at lists dot oasis-open dot org
- Date: Thu, 3 Jun 2004 15:04:57 -0400 (EDT)
- Subject: Re: [docbook-apps] Re: Contents of CVS $Id$
- Reply-to: Diane Larin <diane at inro dot ca>
Hi,
> Here is one solution:
>
> 1. put $Id$ keyword in <releaseinfo> in <*info> (like
> articleinfo/bookinfo...) in a DocBook XML file.
>
> <article>
> <articleinfo>
> <releaseinfo>$Id$</releaseinfo>
> ...
>
> 2. add a 'user.footer.content' template to your customisation layer.
> this is a simple example:
>
> <xsl:template name="user.footer.content">
> <hr/>
> <p class="releaseinfo"><xsl:value-of select="//releaseinfo"></p>
> </xsl:template>
>
> 3. commit the XML file to CVS as usual, then transform it.
Thanks for the solution. It works but not exactly as I want.
I put the $Id$ keyword is the releaseinfo of each of the following:
bookinfo, chapterinfo and sectioninfo (each section is in a separate
file). However, when I am generating the complete book, the information
written in the user.footer.content is that of bookinfo (and not of the
individual files). That is misleading since it looks like all the
files were modified the same date.
Did I miss something?
Diane Larin
diane@inro.ca
To unsubscribe from this list, send a post to docbook-apps-unsubscribe@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/.