GNOME Bugzilla – Bug 333099
Validity errors !!!!
Last modified: 2006-03-08 14:19:13 UTC
Documentation Section: xmllint --valid --noout C/gnome-access-guide.xml C/keynav.xml:1475: element sect2: validity error : Element sect2 content does not follow the DTD, expecting (sect2info? , (title , subtitle? , titleabbrev?) , (toc | lot | index | glossary | bibliography)* , (((calloutlist | glosslist | itemizedlist | orderedlist | segmentedlist | simplelist | variablelist | caution | important | note | tip | warning | literallayout | programlisting | programlistingco | screen | screenco | screenshot | synopsis | cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | constructorsynopsis | destructorsynopsis | methodsynopsis | formalpara | para | simpara | address | blockquote | graphic | graphicco | mediaobject | mediaobjectco | informalequation | informalexample | informalfigure | informaltable | equation | example | figure | table | msgset | procedure | sidebar | qandaset | anchor | bridgehead | remark | highlights | abstract | authorblurb | epigraph | indexterm | beginpage)+ , (refentry* | sect3* | simplesect*)) | refentry+ | sect3+ | simplesect+) , (toc | lot | index | glossary | bibliography)*), got (anchor anchor anchor title para para informaltable ) </sect2> ^ C/keynav.xml:1560: element sect1: validity error : ID keynav-20 already defined <sect1 id="keynav-20"> ^ C/keynav.xml:1671: element anchor: validity error : ID keynav-21 already defined <anchor id="keynav-21"/> ^ C/keynav.xml:1715: element sect2: validity error : Element sect2 content does not follow the DTD, expecting (sect2info? , (title , subtitle? , titleabbrev?) , (toc | lot | index | glossary | bibliography)* , (((calloutlist | glosslist | itemizedlist | orderedlist | segmentedlist | simplelist | variablelist | caution | important | note | tip | warning | literallayout | programlisting | programlistingco | screen | screenco | screenshot | synopsis | cmdsynopsis | funcsynopsis | classsynopsis | fieldsynopsis | constructorsynopsis | destructorsynopsis | methodsynopsis | formalpara | para | simpara | address | blockquote | graphic | graphicco | mediaobject | mediaobjectco | informalequation | informalexample | informalfigure | informaltable | equation | example | figure | table | msgset | procedure | sidebar | qandaset | anchor | bridgehead | remark | highlights | abstract | authorblurb | epigraph | indexterm | beginpage)+ , (refentry* | sect3* | simplesect*)) | refentry+ | sect3+ | simplesect+) , (toc | lot | index | glossary | bibliography)*), got (anchor title para para informaltable ) </sect2> ^ Correct version: Other information:
We've switched to using includes instead of entities to load other XML files. The xmllint command to validate has changed to reflect that IIRC.
... though that's the user guide, not the access guide. Ignore me, it's early in the morning :)
So what Joachim is saying is that the proper xmllint command is this: xmllint --noout --xinclude --postvalid docname.xml Nonetheless, the document is still invalid. The anchor elements need to be placed after the title elements to conform to the DTD.
My fault. Should be fixed in CVS. xmllint now runs cleanly. Closing
Oh, I meant to say something else too. I've said it before, but I'm going to keep saying it over and over and over until everybody knows not to run xmllint manually. Our wonderful build utilities do the proper xmlling command when you do 'make check'. So, you know, spread the word. Thanks for fixing, Don.
*Ordinary docs writer* What's a build utility?
build utility == make and autotools framework == stuff to execute the proper command to create, in example, executable from source code on your system. Note1 - make command can do a lot more if you have UN*X-compliant mind: make command, when invoked, simply run actions on conditions you wrote in a file Note2 - autotools helps you to write conditions files for make command, checking for available and/or needed stuff on your system. (I hope this can help you)