Originally created by: *anonymous
Originally created by: v.villenave
Originally owned by: v.villenave
In the following example, the highest note is correctly printed in the first bar, but in the second bar the accidental is shifted to the left.
:::TeX
\version "2.12.1"
<<
{ gis''1 gis'' }
\\
{ <fis' g'>1 <f' gis'> }
>>
Mark has done some extensive tests on http://lists.gnu.org/archive/html/bug-lilypond/2008-11/msg00039.html.
Originally posted by: v.villenave
A related example from Mark:
"An accidental may move away from its note if there is
an interval of second nearby. The closer the second,
the further the accidental moves. This looks weird!"
Han-Wen:
"Joe, maybe we should increase the slope for the accidental skylines?"
Summary: Wrong accidentals alignment when a second occurs simultaneously
Cc: joeneeman
Last edit: Simon Albrecht 2015-09-28
Originally posted by: joenee...@gmail.com
The behaviour for the first example is explained by the fact that we align accidentals belonging to the same octave. The second example is fixed in git.
Labels: fixed_2_12_2
Status: Fixed
Last edit: Simon Albrecht 2015-09-28
Originally posted by: v.villenave
Hmm. Looks a bit funny though; are we sure we want to keep this rule?
New comment from Mark:
Ted Ross (pp.130-135) demonstrates that the preference is overridden in the presence of a second. The preference to have the lower natural close to its note-head overrides the preference to align the octave. Even in the absence of a second, Ross gives cases where it makes more sense *not* to align the octaves.
(see also attachment)
Last edit: Simon Albrecht 2015-09-28
Originally posted by: v.villenave
(No comment was entered for this change.)
Summary: Request: accidentals in the same octave would look better not aligned (in some cases)
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low
Originally posted by: joenee...@gmail.com
(No comment was entered for this change.)
Labels: -fixed_2_12_2
Status: Accepted
Originally posted by: janek.li...@gmail.com
More examples attached.
Also, the behaviour mentioned in comment #1 is not fixed. Issue 2144 was opened to remember about it.
Related
Issues: #2144
Diff: