GGI DocBook Documentation Style 
===============================

What I think is reasonable to stick to.  We want high-quality docs here.
(I know libggi.sgml doesn't follow all this yet, it's a FIXME.)

Don't use OMITTAG.  Just found out that it's not worth the extra
troubles :-(

Use tab indents to mark lower sections.  Newlines to separate logical
units.

	<ListItem><Para>
		Blah
		Blah
		More...

Neither SGML or DocBook seem to document whitespace handling, but expect
whitespace to be collapsed except in 'literal' elements, because HTML and
Linuxdoc does that too.

Don't use tabs in literal content. Tab handling by renderers is unpredictable.

*ALWAYS* mark up things like <ReturnValue>0</> even if it seems trivial.
That's why the elements are there in the first place.  And you'll never know
what the formatter might want to do with the element; I might like
ReturnValues in italics.

I suggest using the COMMENT element for more 'important' comments than the
normal <!-- --> 
(e.g. FIXMEs and editorial comments, as opposed to formatting peculiarities)

And get your SGML terminology right. ;-)

