Re: Issue 1691 in lilypond: Ugly bars in PDF documents

[lilypond]

Comment #33 on issue 1691 by address@hidden: Ugly bars in PDF  
documents
http://code.google.com/p/lilypond/issues/detail?id=1691

I can break the docs in a number of ways, including using incorrect syntax  
and by putting long unbreakable lines in.  However, we tell people not to  
do this.  The point of this fix is that it improves the docs by fixing  
almost all the examples where line breaks occur.  There are exceptions  
(instrument names, ridiculous bar numbers), but we can fix them manually to  
start with and then tell people how to fix them if they see them in new  
images that they put in.

This change improves the situation considerably and should be pushed.  It's  
like a code change that adds collision avoidance code.  We don't junk that  
because it doesn't fix all collisions; we welcome it as a welcome  
improvement.  This is the same.