On Tue, Jul 14, 2015 at 08:52:27PM -0500, Bruce Dubbs wrote: > Fernando de Oliveira wrote: > >index.xml:125: element sect2: validity error : Element sect2 content > >does not follow the DTD, expecting (sect2info? , (title , subtitle? , > >titleabbrev?) , (toc | lot | index | glossary | bibliography)* , > >(((calloutlist | glosslist | bibliolist | 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 | task | anchor > >| bridgehead | remark | highlights | abstract | authorblurb | epigraph | > >indexterm | beginpage)+ , (refentry* | sect3* | simplesect*)) | > >refentry+ | sect3+ | simplesect+) , (toc | lot | index | glossary | > >bibliography)*), got (title segmentedlist variablelist varlistentry ) > > I've been there a lot of times. Let me reformat for you: > > index.xml:125: element sect2: validity error : > > Element sect2 content does not follow the DTD, > > expecting > (sect2info? , (title , subtitle? , titleabbrev?) , > (toc | lot | index | glossary | bibliography)* , > ( > ( > ( > calloutlist | glosslist | bibliolist | 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 > | task | anchor | bridgehead | remark | highlights | abstract | > authorblurb | epigraph | indexterm | beginpage > )+ , > (refentry* | sect3* | simplesect*) > ) | refentry+ | sect3+ | simplesect+ > ) , > (toc | lot | index | glossary | bibliography)* > ), > > got (title segmentedlist variablelist varlistentry ) > ---------- > The varlistentry is out of place in the sect2. It's likely a misplaced > </variablelist> tag. > > -- Bruce > The error messages for new pages are usually very hard to parse, beyond "something went wrong". I've often spent several hours sorting out a new page (these sort of problems seem to arise when I'm already tired). For a _new_ page, I now usually copy an existing page, perhaps remove or comment parts of it, and then concentrate on getting the indexing to validate (i.e. unique names).
After that, I make several passes through it, changing dependencies and text, adding sections and generally fixing things up. For an existing page, 'svn diff' usually helps me spot the errors if I cannot immediately see them. But for a new page I would now do what I did the last time I changed the perl modules page: at suitable times (when it validates), copy it to a new backup. Then, a diff against the backup will show what I have changed since the backup, and the error must be in those changes. Wash, rinse, repeat until satisfied. Clever people can probably add a new page in one go, whilst doing a couple of other things at the same time. Me, I'm a "bear of little brain"¹ so I have to develop workflows which make things easier for me, and then I have to remember to use them ;) ĸen [1.] Winnie-the-Pooh : kid's books by A.A. Milne -- This one goes up to eleven! -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
