bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1000 in lilypond: send texi2html patches upstream


From: lilypond
Subject: Re: Issue 1000 in lilypond: send texi2html patches upstream
Date: Wed, 21 Apr 2010 13:35:27 +0000

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 cruel and unusual punishment.

For example, look at texinfo_file_name($). Figure out what we're doing differently than a normal texinfo_filename($)... I think it's the lc_last() call. Then send a feature request to the texinfo list asking to have the html filename be lower-cased (but not the intermediate directories; just the filename). Once that's in the main texi2html... and once they have a stable release... then we can remove that function from our file. Oh, and double-check that I'm correct that lc_last() is the only
difference.


Some parts of our file probably shouldn't be merged, like the translations and xref
stuff.


No, this isn't an easy or quick task, but (like all build system issues) it'll only get worse as time progresses. And at least this could be done by a Frog -- you don't need to be a lilypond expert, and certainly don't need to know anything about scheme or C. Just a bit of basic perl knowledge, the ability to compile the docs (to see if the modified texi2html + our changed init file produce the same html files), and
communicating with the texinfo people.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings




reply via email to

[Prev in Thread] Current Thread [Next in Thread]