Re: convert-ly oddities

[Thomas Morley]

2016-12-18 15:08 GMT+01:00 Peter Toye <address@hidden>:
> Thomas,
>
> Thanks. It just looks odd that the convert.ly issued with .52 only updates
> to .49

This is a misunderstanding.

convert-ly from lilypond-2.19.52 _does_ update to 2.19.52.
Or more precisely: all syntax-changes for which a convert-rule exist
are applied up to 2.19.52.
It does not change the version-statement of your file to the
lilypond-version of convert-ly you actually use, but to the version of
the latest convert-rule.

In general, convert-ly converts syntax of ly-files to be compilable
with the LilyPond-version matching the version of convert-ly.
There is no need to change the version-statement to make it compile
with 2.19.52 at all. You could even compile a very old 2.12.3-file
with 2.19.52 (granted the syntax of the old file will work).
The reason to change the version-statement to the version of the
latest convert-rule is more to issue an error, if a converted file is
compiled with an older ly-version, like:
error: program too old: 2.16.2 (file requires: 2.19.52)

Cheers,
  Harm