[Texi2html-bug] Some more questions about texi2html

[Reinhold Kainhofer]

Hi Patrice,
I hope this is the right mailing list for such questions. If not, please tell 
me where to send such questions...

I'm currently trying to make lilypond's documentation build entirely with 
texi2html so that we can finally switch from makeinfo to texi2html. 
My current attempts are at:
    http://kainhofer.com/~lilypond/texi2html-out/
The init file used for this output (containing some really nasty hacks...) is:
   http://kainhofer.com/~lilypond/texi2html-out/lilypond-texi2html.init

There are still some issues I have not yet been able to solve:


-) I modified the navigation buttons to cover two table rows (using some nasty 
hacks in the init file). However, since we are splitting by numbered sections 
(i.e. unnumbered subsections are put into the same file, thanks to the 
element_file_name you gave back in October), I'd like to have the chapter 
navigation ('FastBack', 'FastForward', 'Top',  etc.) line only in the very 
first navigation panel, but not in the panels beween subsections. See e.g.
http://kainhofer.com/~lilypond/texi2html-out/Writing-pitches.html#Relative-octave-entry


-) We want our translated files to have the same chapter/section file names 
(and IDs) as the english version. Currently (i.e. with makeinfo), we have to 
leave all section names untranslated and later on use a python script to 
replace the HTML tags with the proper translations. Of course, we'd like to 
get rid of this had with texi2html. We thought about something like
@node Übung
@chapter Übung
@translationof Tutorial
texi2html would use @nodetranslation for HTML file names and anchors,
and @node for printing it text.
Apparently, in the the element_file_name I don't have access to the contents 
of the current element. How can I do this?
Even better would be, of course, if we could write the @translationof macro so 
that it sets the translationof key of the $element hash that is passed to 
element_file_name.


-) Does texi2html have any support for access keys, i.e. navigating the pages 
with the keyboard (Alt-U for up, Alt-P for previous, Alt-1 for first menu 
entry and so on)? The HTML code looks like

<a rel="next" accesskey="n" 
href="Musical-notation.html#Musical-notation">Musical notation</a>

<a accesskey="1" href="Musical-notation.html#Musical-notation">Musical 
notation</a>


-) Is there any way to get a customized TOC? In particular, the TOC in the 
left "frame" (it's actually a <div> with absolution positioning) is way too 
long, while the overview with only the top-level sections is way too short. 
Idially, each page would get a TOC with the first two levels expanded, plus 
the whole path to the current page expanded.
Also, I would like to add a class="current_toc_page" to the <li> for the 
current page. Is this possible somehow?


-) Not that we need it in our documentation, but still something that I 
noticed: AFAICS, the files names ($docu_toc_frame_file and $docu_frame_file) 
for the frame pages are hardcoded and cannot be adjusted with 
element_file_name, right?


Cheers,
Reinhold

PS: The fact that we can deal with such questions shows how awesome texi2html 
is! it is really a pleasure and so easy to work with it! Thanks for it!

-- 
------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/