Yeah, I agree that there wasn't a total collision in the examples I provided. Perhaps the attached is a bit better. This is what is created when I generate the whole file and not just a little snippet. I tried to boil the example down as much as possible. There is definitely a problem. I can point you to the whole file if needed. Thanks!
-----Jay Anderson On 10/6/06, Graham Percival <[EMAIL PROTECTED]> wrote:
Werner LEMBERG wrote: >>> The bass clef in the following example collides with the rest in >>> the following example. It looks worse in context than it does >>> here, but normally lilypond does a good job of spacing the clef >>> changes. Is there any tweak I can do to fix this or are there >>> deeper problems? Thanks for the help. > IMHO the output is bad, and lilypond should be able to handle this > automatically -- clef changes in similar situations occur far too > frequently in classical music. OK, I've added it, but this is probably a long-term wishlist item. http://code.google.com/p/lilypond/issues/detail?id=110 Cheers, - Graham
collision.png
Description: PNG image
_______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
