Menu
▾
▴
#1000 communicate with upstream texi2html project
Accepted
nobody
None
Maintainability
2015-11-14
2010-01-25
Anonymous
No
Originally created by: *anonymous
Originally created by: percival.music.ca@gmail.com
Our lilypond-texi2html.init file is getting ridiculous; we keep on fixing
texi2html bugs by introducing extra functions to this file. It would be
nice if somebody could communicate with the texi2html people -- send our
bugfixes and features upstream, prod them into releasing 1.84 or whatever,
and then update our file to work with the later version and remove anything
that we don't need in there.
Originally posted by: pkx1...@gmail.com
I mistook this for patches that needed testing on current master. Sorry.
Labels: -Patch-new
Diff:
From Michael Gerdau (on translation list)
I have played a bit with the patches provided in post #26 of Issue #1000
https://code.google.com/p/lilypond/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary&groupby=&sort=&id=1000
Unfortunately google code archived this project so I can't add comments
to it anymore. Thus I'm writing on this list hoping to reach people
who know how to proceed.
What I have found is why
make doc
stops when processing lilypond-git/input/regression/midi
The reason is that the GNUmakefile inside of that directory sports a
line saying
TEXI2HTML_FLAGS += --nomenu
--nomenu is not a valid option for texi2any. I'm not familiar enough
with both tools to really know but from the manpage it seems using
--no-headers instead is what need to be done.
From what I've seen a like reasoning goes for these GNUmakefile
lilypond-git/input/regression/abc2ly/GNUmakefile
lilypond-git/input/regression/midi/GNUmakefile
lilypond-git/input/regression/musicxml/GNUmakefile
FWIW after I replaced '--nomenu' with '--no-headers' the build of
the documentation failed when building out-www/snippets-big-page.html
The resulting logfile snippets.bigtexi.log is roughly 650k. It has lots
of msgs complaining about unreferenced nodes.
These appear for
out-www/pitches.texi
out-www/rythms.texi
out-www/expressive-marks.texi
out-www/repeats.texi
out-www/simultaneous-notes.texi
out-www/staff-notation.texi
out-www/editorial-annotations.texi
out-www/text.texi
out-www/vocal-music.texi
out-www/chords.texi
out-www/keyboards.texi
out-www/percussion.texi
out-www/fretted-strings.texi
out-www/unfretted-strings.texi
out-www/winds.texi
out-www/ancient-notation.texi
out-www/world-music.texi
out-www/contexts-and-engravers.texi
out-www/tweaks-and-overrides.texi
out-www/paper-and-layout.texi
out-www/titles.texi
out-www/spacing.texi
out-www/midi.texi
out-www/template.texi
Aren't all of the above created programmatically ?
And if so:
Has there been a (small) change in syntax from texi2html to texi2any
that now breaks all of these ?
I don't know enough about all these to dig into this any further on my
own. Hopefully someone more knowledgeable than me is able to make use
of what I'm writing here.
Of course if I can be of any further help I'm happy to do whatever
someone knowledgeable advises me to do.
Kind regards,
Michael
From Federico
Hi Michael
They are working on it here:
https://github.com/barrykp/lilypond-texinfo
You may want to contact them, even if I think that they are aware of the issue you are reporting.
The move to the new issue tracker is taking longer than expected. I think that you'll see an announcement on lilypond-user when everything is ready.
From Jean-Charles
Le 25/08/2015 23:46, Michael Gerdau a écrit :
You got further than I did!
The problem comes, IMO, from the 6 first lines of snippets.bigtexi.log
that I don't manage to get rid of once I've modified line 77 from
*normalise_node = sub($)
to
*normalise_node = sub
They read:
Useless use of hash element in void context at
/home/jcharles/GIT/New-texinfo/Documentation/lilypond-texi2html.init
line 1275.
Texi2HTML::Config::generate_ly_toc_entries() called too early to check
prototype at
/home/jcharles/GIT/New-texinfo/Documentation/lilypond-texi2html.init
line 1282.
Use of uninitialized value $Texi2HTML::Config::SPLIT in string eq at
/home/jcharles/GIT/New-texinfo/Documentation/lilypond-texi2html.init
line 604.
Use of uninitialized value $Texi2HTML::Config::SPLIT in string eq at
/home/jcharles/GIT/New-texinfo/Documentation/lilypond-texi2html.init
line 604.
Use of uninitialized value $Texi2HTML::Config::SPLIT in string eq at
/home/jcharles/GIT/New-texinfo/Documentation/lilypond-texi2html.init
line 1917.
Use of uninitialized value $Texi2HTML::Config::SPLIT in string eq at
/home/jcharles/GIT/New-texinfo/Documentation/lilypond-texi2html.init
line 1917.
I'm really not able to go further…
Cheers,
Jean-Charles