Wrong octave and glyphs when printing accidentals

[Maximilian Albert]

Hi,

these might actually be considered two bugs but they are so intimately related
that I decided to report them together.

When manually setting a custom key signature by changing the Staff.keySignature
property as in the example below, 

1) natural signs in front of the notes b and c are printed in the wrong octave
   (too high; this does not apply to other accidentals)

2) the glyphs are not associated to the correct numbers; the numbers can range
   from -4 to +4, meaning double flat to double sharp. However, the values +/-1
   already print double sharp/flat, and bigger values throw an error like
   "no glyph found for alteration: 2".

Both issues only occur in the development, not in the stable version (I tested
with 2.11.10 and 2.10.10). I'm attaching an example illustrating them.

Cheers,
Max



%% 1) Natural sign is placed in the wrong octave
%%        (also if the value 6 is replaced by 5).
%% 2) Accidentals are associated to the wrong numbers 

\version "2.11.10"  % on Debian Linux
\paper{ ragged-right=##t }

\relative c'
{
  \key c \major
  \clef treble
  c2
  % The natural sign occurs in the wrong octave
  \set Staff.keySignature = #'((6 . 0))
  c2

   % This prints double sharp instead of "semi"-sharp
  \set Staff.keySignature = #'((6 . 1))
  c2 

  % This throws error "no glyph found for alteration: 2"
  \set Staff.keySignature = #'((6 . 2))
  c2
}