Issue 379 in lilypond: ugly slur with key signature and linebreak

[codesite-noreply]

Issue 379: ugly slur with key signature and linebreak
http://code.google.com/p/lilypond/issues/detail?id=379

Comment #4 by v.villenave:
New comment from Mark Polesky:

According to Kurt Stone: ties and slurs (including phrasing slurs) at the
end of a line "should stop just before the clef" if there is one; otherwise,
"neither slurs nor ties should extend beyond the barline." Ties and slurs at
the beginning of a line should begin just after the time signature if there
is one; just after the key signature if there is no time signature; just
after the clef if there is neither key nor time signature.

Thus, in the following example, there are at least 6 errors with LilyPond's
rendering:

end of first line:
1. phrasing slur does not stop just before the clef
2. slur does not stop just before the clef
3. tie is so small, it looks like a dot

beginning of next line:
4. slur does not start just after the time signature
5. phrasing slur intersects slur
6. phrasing slur is unnaturally tall

And for my own 2 cents: it's my understanding that there should be a small
amount of space between the last of the front matter and the beginning of
the slurs/ties. In my example, the slurs/ties are all above the staff, so
this issue is less apparent. But when the slurs/ties are in the middle of
the staff, they usually touch the front matter with no space in between.

_________________________________________________


\version "2.11.62-1"
\paper {
 indent=0
 between-system-space=0
 system-count=2
 ragged-right=##t
}
\relative {
 \slurUp \phrasingSlurUp \tieUp
 \key f \major f\( e d( c~
 \clef bass \key g \major \time 2/2 c b) a g\)
}



Attachments:
        line-break-slurs.PNG  7.8 KB



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings