Re: Page breaking fails for multiline embedded score

Another change I was thinking about, is to redesign the API contracts around interpret-markup-list. Right now, we start from the list of markups, and for-each markup, apply the markup function and destructively append! the resulting stencil to the result list under construction. The procedur

Issue 1015 in lilypond: doc line width

Status: Accepted Owner: Labels: Type-Documentation Priority-Low Frog Maintainability New issue 1015 by percival.music.ca: doc line width http://code.google.com/p/lilypond/issues/detail?id=1015 There's some questions/concerns about the default line-width for lilypond in the docs. Investigat

Re: Page breaking fails for multiline embedded score

>> Of course, combine-score-stencils needs a real implementation, not just >> (reverse stencils). Ok, I created a patch: http://codereview.appspot.com/207105 Boris Shingarov Work on Lilypond under grant from Sonus Paradisi / Jiri Zurek (Prague), Czech Science Foundation, Project No. 401/09/041

Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2)

Status: Accepted Owner: Labels: Priority-Low Type-Defect New issue 1014 by brownian.box: Full/multi measure rests should be semibreve (for any but 4/2) http://code.google.com/p/lilypond/issues/detail?id=1014 Was discussed here: http://lists.gnu.org/archive/html/lilypond-user/2008-12/msg0