[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 1133 in lilypond: Long TextScripts and Marks d
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 1133 in lilypond: Long TextScripts and Marks don't behave well with line breaks |
Date: |
Wed, 01 Jul 2015 18:45:42 +0000 |
Updates:
Summary: Long TextScripts and Marks don't behave well with line breaks
Comment #5 on issue 1133 by address@hidden: Long TextScripts and Marks
don't behave well with line breaks
https://code.google.com/p/lilypond/issues/detail?id=1133
I also think that TextScripts (and any kind of Marks) should be breakable.
I figure that this would be easier than to make the entire line-breaking
algorithm aware of the problem, and IMO it's more elegant also. It would
likely be a boolean property 'breakable' as with Beam, #f by default (?).
Alternatively it might depend on length.
(Or, most complicated, a broken TextScript (or similar) should give a
demerit to the line-breaking configuration.)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
- Re: [Lilypond-auto] Issue 1133 in lilypond: Long TextScripts and Marks don't behave well with line breaks,
lilypond <=