David Nalesnik <[email protected]> writes: > On Tue, Dec 3, 2013 at 6:17 AM, David Kastrup <[email protected]> wrote: > >> David Kastrup <[email protected]> writes: >> >> > Here is a scan from a Peters edition of Grieg with somewhat flamboyantly >> > executed slurs (I am almost sure that the engraver had felt some grim >> > satisfaction when doing those). >> > >> > >> > And the tuplet numbers are definitely awful. I tried it with 2.16.2, >> > and the results were either equally awful, or one of the tuplet numbers >> > was written in the middle of the beams. Can't reproduce this right now >> > with -dpreview, however, so whether the tuplet numbers are in the clouds >> > or the beams probably depends on some internal evaluation order. >> > > Here's a workaround for the tuplet number placement issue. Haven't updated > this for over a year, so I'm a little surprised that it still works. I > imagine all of this should be handled in the C++ code, but for what it's > worth...
Thanks but I'm actually not in need of a workaround now: I just stumbled on some audacious manual slurring which is actually too exaggerated to be generally recommended for automated engraving. I'd bet if you showed the bars to someone who worked at Peters at the time, he could tell you _who_ the engraver was, just like insiders can tell who drew a particular Donald Duck comic strip. So I wanted to share the slurs, and then LilyPond surprised me with awful tuplet numbers. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
