On Fri, Dec 20, 2013 at 11:05 AM, David Kastrup <[email protected]> wrote:
> Not really: what's discussed in that thread is what happens when the > bracket-visibility is #f. In that case, the tuplet number is placed as > if there were a bracket, and since that bracket is placed quite far from > the beam in cross-staff situations, the result is awful. > > In the current thread, however, the brackets are visible, and the > results are still awful, and exactly because the brackets themselves are > placed ridiculously. > > Even if the issue in this thread would be fixed, the tuplet numbers in > the references thread would be misplaced. > they probably are related -- the only reason i turned the tuplet brackets on in this case was because i originally couldn't find the tuplet numbers on a very cursory inspection when typesetting this piece. turning the brackets on enabled me to find the numbers and i left them on because i couldn't think of a good place to put the numbers. if you turn the brackets off in this case, then numbers are still in weird places. -- Do not meddle in the affairs of trombonists, for they are subtle and quick to anger.
_______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
