Re: Custom key signature stencils, differentiating major and minor keys

[Paul Morris]

On Nov 16, 2012, at 8:55 PM, MING TSANG <address@hidden> wrote:

Dear Paul,

I tested your latest version, the C Major, A Minor the alternative key signature does not print on the second system. G major, E minor & D Major, B Minor seems ok - that is - alternative key singature displayed on the second system.

Hi Ming,  Yes, I do not know how to work around this.  It seems that in the keys of C Major or A Minor, LilyPond does not print a key signature at all at the beginning of the 2nd, 3rd, etc... lines of music (not even an "empty" or "invisible" key signature).  So the custom key signature engraver does not get called and so it does not print the name of the key there.

-Paul

Please see the .pdf

 

Blessing in+,

Ming.

---

From: Thomas Morley <address@hidden>
To: Paul Morris <address@hidden>
Cc: MING TSANG <address@hidden>; lilypond-usermailinglist <address@hidden>
Sent: Friday, November 16, 2012 7:50:17 PM
Subject: Re: Custom key signature stencils, differentiating major and minor keys

2012/11/14 Paul Morris <address@hidden>:
> Hi Ming,  I took another look at this and since there's only one key
> signature where the accidentals do not extend above the staff (F major / D
> minor) I just added extra padding for those keys.  Now the key names always
> appear above the staff, regardless of the clef.
>
> The sizing of the accidental signs in the key names is better in this
> version as well.
>
> Cheers,
> -Paul

Hi Paul,

am I right you've added your engraver to LSR with a [needs upgrade]-label?
http://lsr.dsi.unimi.it/LSR/Item?u=1&id=856

If so:
I downgraded your code to make it work with 2.14.2:
changing the make-engraver-macro (created by David Kastrup) to the old
syntax and changing the #{ #}-syntax (also made possible by David) to
scheme-syntax.
The 2.16.0-code is untouched and commented.

Note that I didn't have a closer look at the code. ;)
Also note, since there is something strange with the displayed
LSR-output I added a markup to get the spacing correct.

If you agree, I could approve it now.
Currently, I let it unapproved, in case you may want to add or change sth.


Best,
  Harm

<test-custom-key-signature_1.pdf>