Similar issue, but not exact -- 430 is fixed in 2.11.32, but this bug
remains.
http://code.google.com/p/lilypond/issues/detail?id=446
Cheers,
- Graham
Neil Puttock wrote:
Hi Trevor
On 9/2/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
I can't be certain, but I'd bet that this is related to Google #430:
http://code.google.com/p/lilypond/issues/detail?id=430
If it's the same bug, then we're in luck because Han-Wen and Joe have
marked #430 fixed in the upcoming 2.11.32 build.
That certainly looks like a similar issue.
I should have mentioned however that it's only the portato script which
produces this weirdness; I tested it with several other articulations, and
none resulted in broken beams.
Regards,
Neil
------------------------------------------------------------------------
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
