Comment #5 on issue 1000 by percival.music.ca: send texi2html patches
upstream
http://code.google.com/p/lilypond/issues/detail?id=1000
I really, really doubt that anybody is going to volunteer.
*shrug*
Our texi2html init file is a complete mess, but it's no worse than any
other part of
ou
Comment #4 on issue 1000 by markpolesky: send texi2html patches upstream
http://code.google.com/p/lilypond/issues/detail?id=1000
I'd prefer this to be done sooner than later, but I'm not
the one for the job. It looks like the final texi2html
release is imminent* and we don't want to miss it. W
Updates:
Labels: Maintainability
Comment #3 on issue 1000 by percival.music.ca: send texi2html patches
upstream
http://code.google.com/p/lilypond/issues/detail?id=1000
One of us definitely needs to be involved. Throwing the entire init file
at them
without explanations would be cr
Comment #2 on issue 1000 by markpolesky: send texi2html patches upstream
http://code.google.com/p/lilypond/issues/detail?id=1000
Is it just a matter of asking the texi2html guys to look
over the lilypond-texi2html.init file or does one of us
need to get involved and explain some of texi2html bug
Comment #1 on issue 1000 by v.villenave: send texi2html patches upstream
http://code.google.com/p/lilypond/issues/detail?id=1000
[OT but sooo tempting]
And this is our 1000th tracker page! Yay! :)
--
You received this message because you are listed in the owner
or CC fields of this issue, or b
Status: Accepted
Owner:
Labels: Type-Build Priority-Low Frog
New issue 1000 by percival.music.ca: send texi2html patches upstream
http://code.google.com/p/lilypond/issues/detail?id=1000
Our lilypond-texi2html.init file is getting ridiculously; we keep on fixing
texi2html bugs by introducing
