Pavel Roskin <pro...@gnu.org> writes:
> Hello!
>
> I'm using the current lilypond from git. This is what I have before
> the conversion:
>
> \version "2.16.0"
> {
> \override KeySignature #'c0-position = #6
> }
>
> convert-ly turns it into:
>
> \version "2.17.20"
> {
> \override KeySignature.c0-position = #6
> }
>
> The original file can be processed by lilypond, but the converted file cannot.
Small wonder. I thought our default use of symbols matched our naming
rules, but that one's an exception.
We can make an exception for convert-ly here, but that's not a
satisfactorily final solution.
I propose renaming it. Suggestions?
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
