Re: Issue 1180 in lilypond: LM 4.5.3 Real music example needs additional tweak (plus explanation)

[lilypond]

Comment #2 on issue 1180 by address@hidden: LM 4.5.3 Real music  
example needs additional tweak (plus explanation)
http://code.google.com/p/lilypond/issues/detail?id=1180

Your tweak looks fine at first glance.
But: As I mentioned here  
http://lists.gnu.org/archive/html/lilypond-devel/2010-07/msg00214.html (now  
I realize that a forgot to mention it in the issue report, sorry!!!) there  
is a line break in the example on the website.
If I add "ragged-right = ##t" in a \paper section and a manual \break  
before the last bar I get the attached output which is much worse than the  
original. Also if I change the horizontal spacing (by adding a right-margin  
of, say 9\cm the phrasingSlur doesn't fit anymore (because its extent is  
now hardcoded?).

So I think we have a problem with this example.
And I also think it is quite important to find a clear solution to this -  
as it is a point where a newcomer will end up when getting acquainted with  
LilyPond. (Now that I'm writing this I vaguely recall having already been  
annoyed by this phrasingSlur when I first met LilyPond. It didn't stop me  
from being interested, but it could well keep someone else from bothering  
more with LilyPond.)

1)
If someone recreates the example and compiles it, it will look different  
than on the website because it won't have the line break in it.
While this might seem to be neglectable it isn't really straightforward.
2)
It becomes a problem because the phrasingSlur behaves quite differently  
with or without the line break - and needs (different) manual tweaking in  
both cases.
3) So it isn't clear which situation should be addressed by a tweak, the  
one on the website or the one a user would see if he compiles for himself.
Both couldn't easily be explained in the text. Basically there would have  
to be a tweak for the version with line break and a comment going something  
like: "but if you compile it yourself you will have a different  
situation" ...

Ideally the problem should be avoided in the first place, i.e. having the  
example fit onto one system on the website.
If that's not possible one might have to suggest a completely new and  
shorter example for this chapter.
I wouldn't want to demand such a major change (and couldn't contribute one  
neither). But I also think that a new user shouldn't be confronted with  
such a complicated situation.

Or is this after all an issue with the phrasingSlur itself and should get a  
new issue on its own?

So any opinions on the matter highly welcome.
Urs

P.S. When compiling the snippet I noticed another (minor) error in the  
example code: After the last g2. of rhMusic there is a bar check which  
obviously fails and should be removed.

Attachments:
        LM-phrasingSlur.png  22.8 KB