Re: Issue 448 in lilypond: KeyCancellation and KeySignatures in un-necessarily separated columns

[lilypond]

Updates:
	Summary: KeyCancellation and KeySignatures in un-necessarily separated  
columns

Comment #5 on issue 448 by address@hidden: KeyCancellation and  
KeySignatures in un-necessarily separated columns
http://code.google.com/p/lilypond/issues/detail?id=448

For examples I went to Mahler, who loved key changes.  I found that the new  
key signature is run up against the cancellation, even in Edition Peters.   
I find that harder to read than what LilyPond does.

I suggest we want the KeySignatures and KeyCancellations each left-aligned  
in their own columns, but allow those columns to mesh when there is room.   
This would put the es\major signature over the cancellation in the bug  
example, but still align nicely for the situation Mats mentions above.

One implementation would be to have horizontal skylines calculated for  
KeyCancellation and KeySignature for use in  
break-alignment-interface::calc-positioning-done, and change the  
space-alist specification beteween KeyCancellation and KeySignature.