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

[Patrice Dumas]

On Wed, Mar 19, 2008 at 12:40:55AM +0100, Reinhold Kainhofer wrote:
> 
> 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

I have attached a diff for your script, since after some thinking I'd
prefer not to have yet another buttons array in the default case.

> 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.

You can now use the 'unknown' function reference in pass 1 and pass 2.
This should be enough, though you may need to use/set data directly from the
main program. I can give you more help if you want to.

> -) 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

I added this. With variables USE_ACCESSKEY, USE_REL_REV and also added
support for <link> with USE_LINKS. You will have to synchronize your
print_navigation. The acceskey only makes sense when split at nodes,
since if there is more than one element in a file the acesskey will
be the same for all the elements. In your case, you don't split at
nodes, but USE_ACCESSKEY makes sense, so you may want to duplicate the
code where USE_ACCESSKEY is used in texi2html.init to remove the 
if ($SPLIT eq 'node') conditional.

All these features are not used in the default case, but set in
makeinfo.init.

> -) 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?

It is fixed. I also included your de translation.

--
Pat