Re: convert-ly oddities

[Thomas Morley]

2016-12-18 12:54 GMT+01:00 Peter Toye <address@hidden>:
> I've just installed 2.19.52 and put it into Frescobaldi. On converting two
> of my files I got 2 oddities:
>
> 1) (fairly serious) It converted to 2.19.49, not .52

There are no converting-rules for versions higher than 2.19.49 (no need for it)
So convert-ly displays the version where the latest rule was applied.
The version-statement in the .ly-file is changed to this as well.

You can be sure convert-ly did the job up to 2.19.52, there's simply
nothing to do after 2.19.49.


> - I changed the version
> number by hand, but I'd have thought that this should be automatic. The
> message at the bottom of the file is:
>
> %{
> convert-ly.py (GNU LilyPond) 2.19.52  convert-ly.py: Processing `'...
> Applying conversion: 2.19.2, 2.19.7, 2.19.11, 2.19.16, 2.19.22,
> 2.19.24, 2.19.28, 2.19.29, 2.19.32, 2.19.40, 2.19.46, 2.19.49
> %}
>
> 2) (annoying) It inserted a blank line between each of the original lines in
> the file. Could this be because I'm using Windows and the CR-LF newline is
> confusing it? This would appear to be a bug.

Maybe related to Frescobaldi and/or windows. Can't say anything here.
I'm on LINUX and don't use Frescobaldi.
At least I never experienced this behaviour.

Cheers,
  Harm