DocBook - xml questions

[Neil Williams]

On Friday 14 April 2006 6:39 am, Bengt Thuree wrote:
> > 2)We should still follow the guidelines in HACKING?

These were added to support those who want to process the DocBook with SGML 
tools instead of the automated XSL tools.

> > a. Avoid using the XML empty tag, specify the closing tag.
> > 	        e.g. <para></para> instead of </para />
> >
> > ===> <imagedata fileref="figures/XXXX" srccredit="YYY ZZZ" format="PNG"/>
> > ===> ends with a /> in every chapter file.

Could be why the images aren't located by SGML tools.
;-)

> > b. Avoid a newline after <entry> tags.
> > 	        e.g. <entry><para> instead of <entry>\n<para>

Another SGML oddity but I don't have an explanation - it was just something 
that choked the SGML-based parsers that I tried. (docbook2pdf mainly).

> > c. Avoid underscores in id attribute values.
> >  	        e.g. id="getting-started" instead of id="getting_started"
> > ===>  <sect2 id="invest_custom2">
> > ===> Found that sect2 in every chapter have id="xxxx_"

That's the SGML parser again. Again, I don't have a good answer why this would 
be wrong (I can't see that it's actually invalid) but it does workaround the 
SGML problems.

If SGML parsers like docbook2pdf and docbook2html work OK, these guidelines 
can be updated.

-- 

Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20060414/570cfbf1/attachment.bin