cvs commit: doc/en_US.ISO8859-1/books/handbook/eresources chapter.sgml

[Ceri Davies]

On Tue, Apr 08, 2003 at 01:06:12PM -0700, Sean Chittenden wrote:
> > > The doc@ team may want to revisit how lists are advertised.  I
> > > think it'd be prudent to create another set of entities that are
> > > parallel to the a.[listname] entities that are defined as a set of
> > > ulinks to the mailman interface:
> > > 
> > > <!ENTITY a.announce.name "<ulink url='http://lists.freebsd.org/mailman/listinfo/freebsd-announce'>freebsd-announce</ulink>">
> > > 
> > > If I don't hear any objections, I'll add these entities to
> > > doc/en_US.ISO8859-1/share/sgml/mailing-lsits.ent.  Having
> > > frequently used/referenced lists and URLs scattered about strikes
> > > me as a maintenance headache waiting to happen.
> > 
> > I say go for it.
> 
> Cool, thanks: will do.  Quck question about our doc build process... I
> don't have doc building setup on my laptop (on the road) so I can't
> test this 1st, but:
> 
> <!ENTITY a.mailman.listinfo "http://lists.FreeBSD.org/mailman/listinfo">
> 
> <!ENTITY a.advocacy.url "&a.mailman.listinfo;/freebsd-advocacy">
> <!ENTITY a.advocacy "<ulink url='&a.advocacy.url;'>FreeBSD advocacy mailing list</ulink>">
> <!ENTITY a.advocacy.name "<ulink url='&a.advocacy.url;'>freebsd-advocacy</ulink>">
> 
> Is our doc build process be smart enough to handle nested entities
> like that?  I forget if I have to do that or %a.advocacy.url; -sc

That *should* be ok, but if you can send me a patch I'll test it for you.

Ceri
--