Re: [Texi2html-bug] Some more questions about texi2html

[Patrice Dumas]

On Wed, Mar 19, 2008 at 07:53:29PM +0100, Reinhold Kainhofer wrote:
> 
> Okay, sectionnext seems to work, thanks for the hint. However, the problems 
> are now:
> 
> 1) If I start with the top node, it doesn't have any useful keys set, except 
> NodeNext, which appears to point to the first section, fine. Unfortunately, 

In fact it points to the first menu child (as said in the texinfo
manual).

> that node for the very first node does not have any @'section_childs' set 
> (since apparently it comes from a @node and not a @chapter)...

I agree that it is certainly a bug, when the top node is associated with
a @top element which is similar with a @chapter. (When the @node Top is
not associated with a @top or any other sectionning command, then it
should not have any section child). And in lilypond there is a @top, so
the chapters should be the @top children. I'll have a look at it.

> The first chapter (the one obtained with NodeNext) does not have any 
> section_childs and also does not describe the chapter, but the @node before 

Yes, this is expected, it is going through the nodes hierarchy. You can
retrieve the section associated with a node with $node->{'section_ref'}.
But it would be better if the @top element had childs like any other
sectionning element.

> it... All following chapters have section_childs and work just fine. See e.g.
> http://kainhofer.com/~lilypond/texi2html-out/Divisi-lyrics.html
> 
> 2) The indices seem to be split up into multiple chapters, cluttering the TOC 
> with lots of entries at the end, which I don't want printed at all (and which 
> are not printed in texi2html's TOC). Apparently, these index pages are 
> included with sectionnext...

This is expected, and right, since when split, indices lead to the 
generation of new elements at the same level. Just skip the elements
which have $element->{'index_page'}, they have been added as part of
index split.

--
Pat