bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug#335016: Bug reports for texinfo (and 2 wishes)


From: Torsten Bronger
Subject: Re: Bug#335016: Bug reports for texinfo (and 2 wishes)
Date: Tue, 07 Feb 2006 11:06:11 +0100
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

Hallöchen!

Norbert Preining <address@hidden> writes:

> [...]
>
> Using TeX live eplain.texi sources I generated a xml file (all commands
> and files are from texinfo cvs) and got only one error:
>
> eplain.xml:1373: element enumerate: validity error : Element enumerate 
> content does not follow the DTD, expecting (enumarg? , (item | itemize | 
> enumerate)*), got (indexterm item item item )
>       </enumerate>
>                   ^

Hmm... after a look at the source (xml.c, line 1537) I think there
are two issues: First, the "enumarg" seems to be obsolete because it
was replaced by the "first" attribute.  (By the way, the string
"enumarg" only occurs in the DTD in Texinfo's CVS.)

And secondly, the <indexterm> is spurious of course.  Is it allowed
to have index entries before any @item in a list?  If yes, we either
have to add it to the DTD, or makeinfo has to defer all index
entries until the first item is generated.

> With texinfo.txi (etc) I get one error (with many instances):
> texinfo.xml:14897: element menucomment: validity error : Element code is not 
> declared in menucomment list of possible children
>           <menucomment>How to run <code>Info-validate</code>.</menucomment>

menucomment's content model is:

<!ELEMENT menucomment (#PCDATA | para)*>

This is odd.  Apparently @code and things like that are allowed
within menu comments.  (Right?)  Are multiple paragraphs allowed,
too?  I've never seen them.

Tschö,
Torsten.

-- 
Torsten Bronger, aquisgrana, europa vetus            ICQ 264-296-646





reply via email to

[Prev in Thread] Current Thread [Next in Thread]