lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: convert.ly errors


From: Jean Abou Samra
Subject: Re: convert.ly errors
Date: Wed, 14 Sep 2022 20:15:31 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.0

Le 14/09/2022 à 19:47, Jean Louis Thiry a écrit :
Hello everyone,

When using convert.ly <http://convert.ly> (\version “2.23.12”) everything is fine as I do not work on complex scores. But if I compile a 2.19.81 file, for example, converted into 2.23.12 everything goes well except for a few errors (always the same) which seem to have been overlooked by convert-ly during the conversion.
In the case of my old files which compile well with 2.18.2 or 2.19.81,
\override ChordName #'font-series = #’bold

I have to manually transform this declaration into:
\override ChordName.font-series = #’bold

or:top-markup-spacing #'basic-distance=#0
which becomes
top-markup-spacing.basic-distance=#0

The messages are:

    /Users/JLT/Documents/Lilypond/Partitions/Irlandais/Poll
    Ha'Penny/Poll-Ha-Penny.ly:87 <http://poll-ha-penny.ly:87>:23:
    Avertissement : deprecated: missing `.' in property path
    ChordName.font-series
    \override ChordName
    #'font-series = #’bold

    /Users/JLT/Documents/Lilypond/Partitions/Irlandais/Poll
    Ha'Penny/Poll-Ha-Penny.ly:184 <http://poll-ha-penny.ly:184>:19:
    Avertissement : deprecated: missing `.' in property path
    Beam.length-fraction
    \override Beam
    #'length-fraction = #1.2

    /Users/JLT/Documents/Lilypond/Partitions/Irlandais/Poll
    Ha'Penny/Poll-Ha-Penny.ly:185 <http://poll-ha-penny.ly:185>:19:
    Avertissement : deprecated: missing `.' in property path Tie.thickness
    \override Tie
    #'thickness = #3


So my question is: is this an oversight in the writing of convert.ly <http://convert.ly> or is it too complicated to implement this control in the conversion process of convert.ly <http://convert.ly>?




Well, the new syntax has been around for a long time (2012).
convert-ly did have a conversion rule, but in the version where
the change was done, not in the version where the old syntax was
made to actively emit a deprecation warning. It will change
your override syntax if you run it as

convert-ly --from=2.17.5 --to=2.17.6 ...

David, do you think it would be reasonable to put the same
convert-ly rule again for 2.23.11?

Jean





reply via email to

[Prev in Thread] Current Thread [Next in Thread]