Re: lilypond documentation build issue (both 2.18.2 and 2.19.16)
On Tue, Jul 07, 2015 at 12:22:27PM +0200, Dave Plater wrote: On 7/7/15, Dave Plater dplater.l...@gmail.com wrote: Oh, there's a pretty big chunk of custom stuff in lilypond texi2html. See past discussion here: https://code.google.com/p/lilypond/issues/detail?id=1000 is this issue likely to be resolved soon or is it as complex as the guile 2.x issue and I'm going to have to create texi packages to build the documentation? See https://bugzilla.novell.com/show_bug.cgi?id=936870 It's not as complex as guile 2.x. If somebody has basic knowledge of perl (which isn't hard to acquire) and texinfo (essentially just knowing it's a doc format with @commands), and is good at diagnosing and communicating problems, then I would cautiously estimate 20 hours for this task. 10 hours of investigation and rewriting by oneself, plus another 10 hours of creating minimal examples, sending them to the texinfo list to ask for help, then integrating the solutions into the updated thing. This could very feasibly be done by somebody new to lilypond development. oh, two slight snags: 1) once it was updated to the new texinfo, our build scripts will probably need some slight adjustment. That is not do-able by somebody new to lilypond, but I'd estimate 1 hour from a current lilypond developer to get that done. 2) it is possible (or even likely) that texinfo will need to be changed in order for us to do what we want. I'm certain that if somebody has a minimal example of the problem, and a compelling justification for why we want to achieve the desired output, the texinfo people will be happy to add whatever features or bugfixes are required in texinfo. But this *would* add another delay for being able to build lilypond on a stock distribution with texinfo 5.x. (that said, if I'm correct about requiring texinfo changes, this will need to happen at some point so all the more reason to jump on this now) - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Issue 4059: Document MIDI mapping and MIDI effects (issue 249980043 by tdanielsmu...@googlemail.com)
Keith OHara k-ohara5...@oco.net writes: That programmer who added the code didn't know about Lilypond's engraver/performer method of routing events and property-changes to output, and didn't know much about midi, so the data flow doesn't make much sense in the context of Lilypond and MIDI. git log -S midiChannelMapping flags the culprit as a certain Jan Nieuwenhuizen. Our current dearth of development power makes it inadvisable to discourage contributors showing a certain promise. There was obviously a perceived need for this feature: maybe is could better be met with different semantics? If so, which? -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond documentation build issue (both 2.18.2 and 2.19.16)
On 7/7/15, Dave Plater dplater.l...@gmail.com wrote: is this issue likely to be resolved soon or is it as complex as the guile 2.x issue and I'm going to have to create texi packages to build the documentation? See https://bugzilla.novell.com/show_bug.cgi?id=936870 Regards Dave On 3/9/15, Graham Percival gra...@percival-music.ca wrote: On Mon, Mar 09, 2015 at 01:29:39PM +0100, David Kastrup wrote: Petr Gajdos pgaj...@suse.cz writes: If this is relevant, texi2html-5.0/texi2html.pl do not contain sub get_index in contrast of texi2html-1.82/texi2html.pl. Whoa. That one certainly looks like it will need attention soonish. I did not realize that we had what amounts to such a large modification of texi2html in our code base. Oh, there's a pretty big chunk of custom stuff in lilypond texi2html. See past discussion here: https://code.google.com/p/lilypond/issues/detail?id=1000 Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel On 7/7/15, Dave Plater dplater.l...@gmail.com wrote: is this issue likely to be resolved soon or is it as complex as the guile 2.x issue and I'm going to have to create texi packages to build the documentation? See https://bugzilla.novell.com/show_bug.cgi?id=936870 Regards Dave Excuse this email mess, I'm forced to use gmail's web site. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCHES: Countdown for July 11th 2015
Hello,
Here is the current patch countdown list. The next countdown will be
on July 11th.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaitingcolspec=Patch%20Owner%20ID%20Summarysort=patch
PUSH:
Dan Eble: Disentangle some Tie and Semi_tie code
http://code.google.com/p/lilypond/issues/detail?id=4478
Dan Eble: autochange looks ahead by only one rest
http://code.google.com/p/lilypond/issues/detail?id=4476
David Kastrup: Move ly-syntax-constructors into separate module
http://code.google.com/p/lilypond/issues/detail?id=4474
David Kastrup: Let \mark and Mark_engraver act consistently
http://code.google.com/p/lilypond/issues/detail?id=4472
COUNTDOWN:
David Kastrup: Reorganize Music_function::call
http://code.google.com/p/lilypond/issues/detail?id=4482
James Lowe: Web: Updated introduction.itexi - Easier Editing
http://code.google.com/p/lilypond/issues/detail?id=4479
Dan Eble: Avoid treating x as relative in \relative { \autochange {x} }
http://code.google.com/p/lilypond/issues/detail?id=4475
Keith OHara: upgrade fixcc.py to astyle version 2.04
http://code.google.com/p/lilypond/issues/detail?id=4383
Keith OHara: examples need explicit \relative c'' {} to copy and paste
correctly
http://code.google.com/p/lilypond/issues/detail?id=4371
REVIEW:
Dan Eble: Refactor \partcombine and \autochange iterators
http://code.google.com/p/lilypond/issues/detail?id=4485
David Kastrup: parser.yy: reimplement MAKE_SYNTAX using with_location
http://code.google.com/p/lilypond/issues/detail?id=4483
David Kastrup: Engraving ends too early
http://code.google.com/p/lilypond/issues/detail?id=4419
David Kastrup: Lyrics iteration can’t handle some unusual setups
http://code.google.com/p/lilypond/issues/detail?id=2608
WAITING:
Urs Liska: Patch: Issue 3916: Add \alternatingTimeSignatures
http://code.google.com/p/lilypond/issues/detail?id=3918
Mike Solomon: Patch: Prevents vertical axis groups with empty skylines
http://code.google.com/p/lilypond/issues/detail?id=3156
Mike Solomon: Patch: Removes the translate_axis call from
axis-group-interface outside-staff positioning.
http://code.google.com/p/lilypond/issues/detail?id=3134
Valentin Villenave: Attach lilypond source in pdf
http://code.google.com/p/lilypond/issues/detail?id=2643
Thank you,
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
