It seems very un-Lilypond-like for the output to be so unpredictable, given that the order is well defined most of the time. It is hard to predict from the code when Lilypond will violate the specified order, so the only real solution is to combine expressions into a single markup 100% of the time. IMO this workaround amounts to deprecating the use of multiple TextScripts as undefined behavior.
On Sun, Feb 18, 2018 at 3:30 AM, David Kastrup <d...@gnu.org> wrote: > Saul Tobin <saul.james.to...@gmail.com> writes: > > > That's a reasonable workaround, but it's not semantic. A single column > > markup is appropriate for one expression split across lines IMO. If it's > > multiple expressions communicating distinct things, it makes sense to > keep > > them separate, particularly if one or more of them are predefined > markups. > > If their vertical order is seminal to the reading, you need to either > make them a single markup or give them different outside-staff-priority > values. > > -- > David Kastrup >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
