This is the LibGGI documentation in DocBook format README.

Software requirements:

	FOR WRITING DOCBOOK:
	(well, you obviously just need an editor, but
	 probably want to validate when you're finished :-)

		* James Clark's SP (SGML parser)
		* DocBook 3.x DTDs

	FOR HTML OUTPUT:

		* Jade 1.1 or higher (DSSSL processor)
		* Norman Walsh's Modular DocBook Stylesheets

	FOR MAN OUTPUT:

		* SGMLSpm (Perl modules for parsing SGML)
		* docbook2man-spec.pl (included here; used with sgmlspl)


In the future, SGMLtools (>=1.1.x) will automate the processing and
formatting of DocBook documents.  For now, I'm just calling nsgmls (SGML
parser) and Jade (DSSSL processor) directly -- your Mileage May Vary.

Assuming nsgmls and the DocBook DTD has been installed correctly,
the following command validates the document:

	nsgmls -s libggi.sgml


To output a HTML version, do:

	jade -t sgml \
		-d /usr/local/share/sgml/stylesheets/docbook/html/docbook.dsl\
		libggi.sgml

	(replace with your correct path to docbook stylesheets, of course.)

The included Makefile automates this somewhat.

I'm working on a Perl script, docbook2man-spec.pl, to do simple
*roff/manpage output. You won't need Jade for this; well, until Jade gets a
_real_ groff/troff backend.

I know the Perl script is slow, not scalable, etc., but it will have to
serve for now.  I can also see many minor glitches with the groff -man
output it generates, but I _don't_ want to hear about them unless you can
pinpoint what is exactly wrong with the groff *source* or you can suggest a
fix to docbook2man-spec.pl.  I simply don't know enough about writing
manpages to do anything useful with 'newbie' bug reports.

