> (On why <articleinfo> loses <date> element with jade...)
 > 
 > On Mon, Aug 08, 2005 at 07:03:03PM -0700, Debian Bug Tracking System wrote:
 > > I discovered recently that this is a function of the DocBook DSSSL
 > > stylesheets, which has the following definition:
 > > 
 > > (define (article-titlepage-recto-elements)
 > >   (list (normalize "title")
 > >         (normalize "subtitle")
 > >         (normalize "corpauthor")
 > >         (normalize "authorgroup")
 > >         (normalize "author")
 > >         (normalize "releaseinfo")
 > >         (normalize "copyright")
 > >         (normalize "pubdate")
 > >         (normalize "revhistory")
 > >         (normalize "abstract")))
 > > 
 > > This is the list of elements that will be included from the articleinfo
 > > element on the titlepage.  You can redefine this to include other elements 
 > > in
 > > articleinfo, like date, if you like.
 > > 
 > > If you have the docbook-dsssl-doc package installed, go to
 > > file:///usr/share/doc/docbook-dsssl-doc/custom.html for details.
 > 
 > Oh.  According to the docbook definitive guide
 > (/usr/share/doc/docbook-defguide/html/artheader.element.html), the
 > <article> element can contain many more elements than listed here.
 > 
 > Should these be reassigned as a bug against the docbook-dsssl package,
 > then?

Hmm, I don't recall getting an email for this, and I just searched my email
folders for it.  That's why I did not respond sooner.  Sorry about that.

Anyway, I don't think this should be reassigned to docbook-dsssl because I
don't think it is a bug at all (that's why I closed it).  The list above is
the _default_ list of elements that will appear on the titlepage of an
article, but you are free to redefine it to include any elements that can be
included in an <articleinfo> element (not the <article> element as you wrote;
was that a typo?).  Redefining things like this is a common way to customize
DocBook stylesheets.

-- 
Neil Roeth


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to