Xavier Scheuer <x.scheuer <at> gmail.com> writes: > > On 8 January 2011 13:33, Daniel Meyer <kontakt <at> djmeyer.de> wrote: > >> % If you write a note with an accidental > >> % and use the same note in the next measure, > >> % the accidental should be reprinted. > >> % When using \partial, it is not reprinted. > > \partial goes back in time and thus make LilyPond think your es4 is > in the same measure as es1 . > Since an accidental is not reprinted in the same measure, LilyPond does > not reprint your accidental. > Repeating what Xavier said because it is so true.
This is the second report within a month of this issue. There are situations, especially around repeats, where common practice music uses partial-length bars and accidentals are reset at the barlines. The 2.12 manual wrongly suggested \partial for these situations, so Mark fixed the 2.13 manual (http://code.google.com/p/lilypond/issues/detail?id=1090). Issue 355 mentions the problem with accidentals in the discussion, but the main point was something else so 355 it might resolve without helping people in the Daniel's (original poster) situation. 2.13.30+ gives a warning, but current manual leads one to the code below, which bypasses the warning but fails to print the barline So it looks to me like we need a new issue. %% The final f-sharp should have a sharp sign %% if it follows a printed barline \version "2.13.46" \relative c' { \partial 8*1 fis8 | fis1 | \set Timing.measurePosition = #(ly:make-moment -7 8) fis2. gis8 } % Workaround: use a *positive* measurePosition to move time forward % \set Timing.measurePosition = #(ly:make-moment 1 8) % as described in versions after 2.13.30 of Notation Reference 1.4.1 % Suggested choices for resolution: % Rename \partial to indicate its baking-up nature, \anacrusis or \pickup % Define a new function \shorten with syntax of \partial but moving forward % Document a correctly shortened bar, and point % to that example near the teaching of \partial _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
