X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=input%2Fregression%2Fdots.ly;h=65a97fb918296d4c5632ce9baad121f2e75e4b03;hb=750b714488c5af6eae22d07163bba8b554734ac6;hp=1e3bc351f990f09fc5d5762f3135963c98ecffb9;hpb=ea8506894a420e3393858a3ee284ab6b2f12c6d6;p=lilypond.git diff --git a/input/regression/dots.ly b/input/regression/dots.ly index 1e3bc351f9..65a97fb918 100644 --- a/input/regression/dots.ly +++ b/input/regression/dots.ly @@ -1,32 +1,40 @@ -\version "1.7.18" -\header{ -texidoc=" -Noteheads can have dots, and rests can too. Augmentation dots should -never be printed on a staff line, but rather be shifted vertically. They -should go up, but in case of multiple parts, the down stems have down -shifted dots. (Wanske p. 186) In case of chords, all dots should be in -a column. The dots go along as rests are shifted to avoid collisions. +\version "2.19.21" \header{ + + + texidoc=" Both noteheads and rests can have dots. + Augmentation dots should never be printed on a staff line, +but rather be shifted vertically. They should go up, but in case of +multiple parts, the down stems have down shifted dots. In case of +chords, all dots should be in a column. The dots follow the shift +of rests when avoiding collisions. + +The priorities to print the dots are (ranked in importance): + +@itemize @bullet +@item keeping dots off staff lines, +@item keeping dots close to their note heads, +@item moving dots in the direction specified by the voice, +@item moving dots up. +@end itemize + " } -\score { - \context Voice \notes\relative c'' { - \time 6/8 - d4. g,, - <>4. <> - <> <> - - - \context Staff < - \context Voice = VA { \stemUp f'' <> r4. } - \context Voice = VB { \stemDown b, <> r4. } - > - - - } - \paper { } - \midi { } +\context Voice \relative { + \time 6/8 + d''4. g,, + \stemDown + 4. + + + + << + { f r4. }\\ + { b, r4. } + >> + + } -%% new-chords-done %% +