Hi, I added the following bug to the database, as custom-key-signatures. I marked it 'critical' because it breaks a regression test.
%critical [EMAIL PROTECTED] \header { texidoc = " When a custom key signature is used, and the octave is set, then the accidental has no effect on the music. The c should get a natural sign, just like the d gets. Also, the fis accidental of the first key signature is not even displayed. " } \version "2.2.1" \score { \notes \relative c' { \set Staff.keySignature = #'(((1 . 2) . 2) ((0 . 3) . 2)) f \set Staff.keySignature = #'(((1 . 0) . 2)) c' \set Staff.keySignature = #'((1 . 2)) d } } On Wednesday 12 May 2004 09.58, Karl Grill wrote: > Hi, > I'm interested in oriental (Turkish) music, and this uses some fairly > non-stndard key sgnatures, so I use key-signature-scordatura.ly as a > template to generate my own keys. I have some problem with the > original file, however. Namely, from the source, I'd figure that the > first key signature should have two accidentals - a quarter sharp at > the high e and a quarter b at the low f - but only the first shows up > in the printed output (not only on my machine, but also in the picture > shown at the website). I'm not familiar with the fine points of music > notation, so this may not be a bug but a feature. I do not htink so, > however, because when I reverse the order of the two accidentals in > the source file, suddenly both accidentals show, but with rather > awkward spacing. So, I figure that this may simply be a spcing > problem, and the missing accidental gets covered by some other item > (maybe the clef, or the other accidental). > > > > _______________________________________________ > bug-lilypond mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/bug-lilypond _______________________________________________ bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond