Hello, On 22 January 2012 09:37, Tobias Leupold <[email protected]> wrote: > Thomas Morley <[email protected]> wrote: >> Of course the upgrade was suggested. But it doesn't >> solve the problem. >> 2.12.3 cuts off the markup (see the first attached png) >> 2.14.2 moves the NoteColumn (see the second png). This is ugly, too. >> (same with 2.15.20) > > That's what I mean. I don't think it's "ugly" -- I would expect Lilypond to do > exactly that. Add additional space, so that the markup can be added completely > to the measure (as James said) > > [email protected] wrote: >> For now, no - it's codable into lilypond's spacing engine but'd take some >> time. Why not just put a \noBreak at the end of the bar? It'll prevent the >> spillover in most cases. > > That's the solution for my problem -- so simple I didn't sse it ;-) > But anyway, it's not really "nice" in my opinion, a good solution would be > what Thomas wrote: > > Thomas Morley <[email protected]> wrote: >> But I was looking for an automated optional method to insert \break >> before the bar with the long markup-text, as Tobias requested in his >> initial mail. > > That's it!
Ah now *that* makes sense to me :) and was the missing part (at least if it was implied, I missed it). Obviously there would be other 'knock on' effects but that would be for another discussion. Isn't this 'kind of/sort of' what the pageturner engraver does - it calculates 'something' to know when to insert a pagebreak http://lilypond.org/doc/v2.14/Documentation/notation/optimal-page-turning Maybe this is the place to possibly add a function like this? (just sowing ideas) :) James -- -- James _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
