Re: convert-ly produces invalid output for KeySignature.c0-position

[David Kastrup]

Pavel Roskin <address@hidden> writes:

> Quoting David Kastrup <address@hidden>:
>
>> Pavel Roskin <address@hidden> writes:
>>
>>> By the way, setting KeySignature.c0-position with \override doesn't
>>> work.  I had to resort to setting it in Scheme:
>>
>> Given the analysis in a longer mail, I revert my opinion that we need to
>> do something here.  c0-position for the relevant grobs _can't_ be set by
>> overrides or tweaks.  Renaming it to middleCPosition would likely cause
>> more confusion.  What _is_ wrong is that the Internals Reference calls
>> it a user property: as far as I can see, it is for internal use only.
>> The question is where this distinction is established.
>
> I just hope you won't take away the ability to adjust the key
> signature without placing the accidentals manually.

It would appear that you can adjust the key signature just fine by using
the _intended_ context variables for that.

> It turns out the LSR snippet 792 would show the initial key signature
> incorrectly.  http://lsr.dsi.unimi.it/LSR/Item?id=792

That snippet does not touch _any_ of the clef-related positioning
variables.  At any rate, I'd do it akin to

\relative c {
  \grace { \clef "treble" s4 }
  \clef bass
  c4 d e f
  g a b c
  % This should be visible
  \clef treble
  d e f g
}

and file a bug because of the unconvincing result:

-- 
David Kastrup