[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook] DocBook documents in CVS
Kai Schröder wrote: > Hi all, > > what is the best solution to use CVS keyword expansion together with DocBook? > > To put $Date$ in //bookinfo/date is clear, but what tags are for $Revision$ > and $Log$? There is the revhistory tag, but how to fill using keyword > expansion? We (ab?)use the revhistory element the following way: <articleinfo> ... <revhistory> <revision role="cvs"> <revnumber>$Revision: 1.7 $</revnumber> <date>$Date: 2004/08/16 13:08:45 $</date> <authorinitials>$Author: rune $</authorinitials> </revision> </revhistory> <xi:include href="setup.rev"/> ... </articleinfo> The first revhistory contains information on the working copy of the file, using standard CVS keywords. We don't show the commit message there. The file setup.rev contains another separate revhistory with role="cvshist". It is legal to have multiple revhistory elements in the *info elements. The .rev files are automagically generated via our general Makefile with help from the excellent Perl script cvs2cl.pl[1]. cvs2cl.pl can generate XML output, and a small and very simple stylesheet transforms this to a revhistory with a revision element for each of the first N revisions in the output from cvs2cl.pl, where N is given as a stylesheet parameter. After some customization of the stylesheets, we have the result you can see on the first page of the attached document. The document is in Danish, but you should be able to find the relevant parts :-) I hope the above is understandable, short as it is. If not, don't hesitate to contact me! Best regards, Rune Lausen, Mikro Værkstedet Denmark [1] http://www.red-bean.com/cvs2cl/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]