Re: Issue 1618 in lilypond: unpredictable placement of rests

[lilypond]

Updates:
        Labels: -Priority-Critical Priority-High

Comment #2 on issue 1618 by address@hidden: unpredictable placement of  
rests
http://code.google.com/p/lilypond/issues/detail?id=1618

Quite possibly the problem existed in 2.13.48, and my testing missed it.   
Testing for inconsistent output is difficult, because the inconsistent  
output is sometimes by chance consistent.

Other reasons to make this non-critical are:
1) it occurs only in complicated cases where LilyPond needs the user's  
help, probably substitution skips or pitched rests, to produce  
easily-readable output, as logged in issue 1547 and issue 384.
2) LilyPond issues a collision warning referring to rests that have the  
inconsistent output.  So even if output consistent with 2.12, it was only  
consistently /good/ by accident.

I don't know any approach better than debug printf()s in  
rest-collision-engraver.cc.  This issue looks very much like issue 1031.