Hi, According to Gardner Read: "It is not necessary to repeat the accidental before a tied note . . . The one exception to this general rule occurs when the note or notes affected by the accidental and tied over the barline come at the end of a system or at the bottom of the page. It is helpful to the performer if the accidental is repeated . . . " (Music Notation, p.131)
I know I have spent a lot of time adding these accidentals in Finale (and redoing them whenever the layout changed), and I very much appreciate that 2.12.2 takes care of them automatically! On Fri, Oct 2, 2009 at 9:12 PM, Joe Neeman <joenee...@gmail.com> wrote: > On Thu, 2009-10-01 at 13:53 -0700, Jonathan Wilkes wrote: > > On Saturday 30 May 2009 10:23:31 pm Werner LEMBERG wrote: > > > > shortest note playing here.") > > > > (shortest-starter-duration ,ly:moment? "The duration of the > > > > shortest note that starts here.") > > > > + (hide-tied-accidental-after-break ,boolean? "If set, an > accidental > > > > +that appears on a tied note after a line break will not be > displayed") > > > > (side-axis ,number? "If the value is @code{#X} (or > > > > addr...@hidden@code{0}), the object is placed horizontally next to > > > > the other object. If the value is @code{#Y} addr...@hidden@code{1}, > it is > > > > > > Joe, items in define-grob-properties.scm are sorted alphabetically. > > > Please move it to the right location. > > > > Oops, I had originally named it show-tied-accidental-after-break. > > > > Thanks, > > Joe > > > > Hi Joe, > > I have a quick question about this property you've added (which is > > wonderful, btw): > > 1) Should tied accidentals after line breaks be suppressed by default? > > I don't know; that was the previous default value, so I left it the > same. I don't mind particularly if someone wants to change it. > > > I've looked through some scores, and even thought there's more examples > > than I thought there would be that show tied accidentals after breaks > > (mainly orchestral scores, and mainly 20th century pieces from the 70s) > > it seems in the vast majority of cases they aren't shown. > > > > On a related note, I like your original property name above, but I guess > it > > would cause problems to change it now. > > Again, I won't object if someone else wants to change it (as long as > there's a convert-ly rule). > > Joe > > > > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user