[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 726 in lilypond: Wrong accidentals alignment when a second occ
From: |
Mark Polesky |
Subject: |
Re: Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously |
Date: |
Sun, 11 Jan 2009 16:15:06 -0800 (PST) |
> Comment #2 on issue 726 by joeneeman: Wrong accidentals alignment when a
> second occurs simultaneously
> http://code.google.com/p/lilypond/issues/detail?id=726
>
> The behaviour for the first example is explained by the fact that we align
> accidentals belonging to the same octave.
But that's wrong! Aligning octave-accidentals may be a
general preference, but Ted Ross (pp.130-135) clearly
demonstrates that the preference is overridden in the
presence of a second (labeled A in the scan). 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. I've
marked these with a red "x" in the picture.
So I propose we remove the auto-octave-accidental-
alignment rule and follow Ted Ross as closely as
possible.
I don't consider this issue "fixed".
- Mark
Ross_accidentals.png
Description: PNG image
- Re: Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously,
Mark Polesky <=