Re: convert-ly oddities

2016-12-20 Thread Peter Toye
Thomas, I've checked using the Windows command line and the spurious newlines don't occur. It's presumably a Frescobaldi issue, so I'll go to Wilbert for more help. Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com - Monday, December 19, 2016, 10:15:41 PM, you

Re: convert-ly oddities

2016-12-19 Thread Federico Bruni
Il giorno lun 19 dic 2016 alle 23:40, SoundsFromSound ha scritto: Me neither, and I use Linux and Frescobaldi (version 3 from master). So probably some Windows issue. Where did you find Frescobaldi v3? I thought the next version (yet to be released) was v2.20 - did I miss something? I ru

Re: convert-ly oddities

2016-12-19 Thread SoundsFromSound
ght the next version (yet to be released) was v2.20 - did I miss something? - composer | sound designer LilyPond Tutorials (for beginners) --> http://bit.ly/bcl-lilypond -- View this message in context: http://lilypond.1069038.n5.nabble.com/convert-ly-oddities-tp198148p198205.html Sent fro

Re: convert-ly oddities

2016-12-19 Thread Thomas Morley
2016-12-19 11:35 GMT+01:00 Peter Toye : > Thomas, > > Thanks - I've just found the version number issue hidden in the Usage > manual! > > But the double newline issue is still an annoyance - it seriously reduces > the amount of text I can get on a screen. I've looked at the files with a > hex edito

Re: convert-ly oddities

2016-12-19 Thread Peter Toye
Thomas, Thanks - I've just found the version number issue hidden in the Usage manual! But the double newline issue is still an annoyance - it seriously reduces the amount of text I can get on a screen. I've looked at the files with a hex editor and it's interesting. I'm using Frescobaldi to gen

Re: convert-ly oddities

2016-12-18 Thread Thomas Morley
2016-12-18 15:08 GMT+01:00 Peter Toye : > 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

Re: convert-ly oddities

2016-12-18 Thread Peter Toye
Thomas, Thanks. It just looks odd that the convert.ly issued with .52 only updates to .49 - I'm not an experienced LilyPonder you know :-) Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com - Sunday, December 18, 2016, 12:28:57 PM, you wrote: > 2016-12-18 12:

Re: convert-ly oddities

2016-12-18 Thread Anders Eriksson
On 2016-12-18 12:54, Peter Toye wrote: convert-ly oddities I've just installed 2.19.52 and put it into Frescobaldi. On converting two of my files I got 2 oddities: 2) (annoying) It inserted a blank line between each of the original lines in the file. Could this be because I&#x

Re: convert-ly oddities

2016-12-18 Thread Federico Bruni
Il giorno dom 18 dic 2016 alle 13:28, Thomas Morley ha scritto: 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

Re: convert-ly oddities

2016-12-18 Thread Thomas Morley
2016-12-18 12:54 GMT+01:00 Peter Toye : > 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-l

Re: convert-ly oddities

2016-12-18 Thread Anders Eriksson
On 2016-12-18 12:54, Peter Toye wrote: convert-ly oddities 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 - I changed the version number by hand, but I'd have thought

convert-ly oddities

2016-12-18 Thread Peter Toye
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 - 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: %{