Hi, FWIW, this seems to be a regression; I have an old PDF made with LilyPond version 2.4.2 that don't show this behaviour. I don't recall using any workaround then, but we're talking early 2005 here, and my source file wasn't under version control then. There's no workaround in the file now, anyway.
I have an even older PDF (probably from 2.2 or 2.0) that show behaviour similar to what I reported, though. Seems this was fixed some time before 2.4.2 and regressed some time after 2.4.2... -- Arvid _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
