2008/7/29 Dominic Neumann <[EMAIL PROTECTED]>: > Okay, then it breaks already after the fourth note ... this doesn´t help much. > Now I added some more \noBreak commands after other notes and now it > fits into one line. > That´s not what I would call a "clean solution" ... :-/ >
I haven't played with chant in lilypond for a while, but I think I remember that it still uses the default time signature (4/4) and note length (crochet or quarter-note) even though these don't mean anything in this notation. What you are seeing is the line being broken at the (unprinted) bar lines, which occur every 4 crochet notes. (Note that the podatus on 'un-' of 'unheil' is two notes.) An even more unfortunate side effect of this is that if you have long melimata the spacing gets messed up, because lilypond allocates a certain amount of space for each neume even though they are clustered together. You can see this in your example, where the notes above 'unheil' have too much space between them. I found that there was no real 'clean solution'. I tended to have a lot of \bar "" commands after various notes more or less around the place where I expected line breaks to occur. Unfortunately, I don't think chant is very high on the list of priorities with the developers and, to be fair, there probably isn't really a compelling reason why it should be. I did have a look at it once but I don't know enough about scheme, python or chant notation to be able to get very far. Regards, Joe _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
