Re: 64-bit Mac build of 2.20 is now available! (convert.ly issue)

[David Kastrup]

David Kastrup <address@hidden> writes:

> Zone Dremik <address@hidden> writes:
>
>>  Thank you David, Marnen, David and Carl for your excellent
>> suggestions and helpful examples. (I will definitely be using more
>> variables in the future.)
>> For the convert.ly issue, your recommendations inspired me to try
>> using BBE. The multi-file search & replace function worked very well
>> (this was with the free version of BBE, so I was very impressed).
>>
>> Further note:
>> I ran a few more of the older files through convert.ly and found
>> that it is finding & updating other instances of obsolete syntax,
>> beyond the two that are missing.
>>
>> Here is a code sample, before & after, for a successful convert.ly:
>>
>> \version "2.12.2"
>> \include "english.ly"
>>  \override LyricText #'font-shape = #'italic
>>
>> \version "2.20.0"
>> \include "english.ly"
>>  \override LyricText.font-shape = #'italic
>>
>> (A side note: By mistake, I ran the compile before convert.ly and
>> was surprised that the Lilypond 2.20 didn't reject the obsolete
>> syntax. I definitely don't have any other versions installed on this
>> machine.)
>
> Yes, overrides and reverts are properly converted.  It's the naked
> assignments that seemed too indistinctive to warrant a generic rule for
> the conversion (there was one used for one-shot conversion of LilyPond's
> own documentation where one can keep the effects in check).

Ok, it seems like (almost?) exclusively variables ending in "-spacing"
are affected here.  That should make a reasonably safe rule
comparatively easy to design.

> I have it on my to-do list to do something here for the sake of
> 2.20.1, but I'm currently laboring on getting 2.21.0 out first: that's
> also urgent.

-- 
David Kastrup