2016-12-19 11:35 GMT+01:00 Peter Toye <[email protected]>: > 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 generate the > files, and it seems that this uses only hex 0A as a line delimiter (very > Unix). Convert-ly replaces this with hex 0A 0A. But it's not consistent, and > I don't recall this happening in previous conversions. The snippets below > show the differences. I'd like to report this as a bug, but the link to > gmane on the LP website is broken.
I could forward this to the bug-list, though you could try to send it to [email protected] yourself, even if not subscribed it will probably get through. Though, I'm not convinced about a LilyPond-bug. Please recheck without using Frescobaldi. Cheers, Harm > > \version "2.18.2" > \score { > > \layout {} > \midi {} > } > > \version "2.19.49" > \score { > > > \layout {} > > \midi {} > } > > > %{ > 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 > %} > > > Best regards, > > Peter > mailto:[email protected] > www.ptoye.com > _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
