Patrice Dumas <pertu...@free.fr> writes: > I am surprised that it using the node up NodeUp direction instead of > the section up Up direction changes the href. I haven't tested, but > unless there are nodes without associated sections, it should be the > same.
Note, my nodes currently all have a custom "up" direction: @node NAME, , , CUSTOM > That being said, some difficulties are inherent, as coding using a > peculiar API is needed, which necessarily requires time to understand. That, plus Perl. :) The documentation is precise, which is fantastic, but it could use some *inline* idiomatic examples, e.g. this is how you add a button to your navigation bar. P.S. Another point of friction was MathJax, namely its *hard-coded* configuration. I ended up pointing `MATHJAX_SCRIPT' to a dummy file, and then configuring and loading MathJax myself in `EXTRA_HEAD'. Speaking of MathJax, Texinfo puts each `displaymath' inside a `div' and `em', so with no-JavaScript browsers, and text readers, such fragments become LaTeX code with *no line breaks*, which makes them hard to read. Perhaps Texinfo could put displayed mathematics into some HTML element that preserves line breaks? Rudy -- "Genius is 1% inspiration and 99% perspiration." --- Thomas Alva Edison, 1932 Rudolf Adamkovič <rud...@adamkovic.org> [he/him] http://adamkovic.org
