Updates:
        Labels: Patch-new

Comment #1 on issue 3000 by [email protected]: Explain how to suppress cautionary accidentals following an explicit key change
http://code.google.com/p/lilypond/issues/detail?id=3000#c1

Doc: cautionary accidentals after a key change (3000)

  Add text and examples to NR 5.4.6 "Using break-visibility"
  to cover the printing of cautionary accidentals following
  an explicit key change.

  (Thanks to Paul Morris for the suggestion)

http://codereview.appspot.com/6872049


Reply via email to