Re: Lilypond 2.16 and 2.18 incompatibility for \relative without absolute note outside the score

[Mark Veltzer]

Unfortunately I cannot use convert-ly, since on a large project such as I am working on I am using an extra pre-processor before handing out the output to lilypond.
This means that my "source" files are not in lilypond format but only contain snipplets of lilypond code.
I actually imagine that every large scale lilypond project would do something like this.

You can check this out at https://github.com/veltzer/openbook

What I'm basically saying here is that the whole approach of convert-ly is dubious since it assumes that people are using lilypond a certain straightforward way.

I understand the motivation of convert-ly: it allows you guys to break backwards compatibility. But you are still breaking backwards compatibility and it hurts.

A better way would have been to make the new lilypond support more features but retain old behaviour until old behavior goes away gradually.

If that was the case I would not need to edit my files.

Cheers,

   Mark

On Tue, Nov 4, 2014 at 5:25 PM, Matthias Böhringer <address@hidden> wrote:

Hello Mark,

you do know about convert-ly?

HTH, Matthias

Am 04.11.2014 um 16:15 schrieb Mark Veltzer:

Hello all,

Just moved to ubuntu 14.10 (utopic) and got lilypond 2.18.2 instead of
2.16.2 that was installed on ubuntu 14.04 (trusty). This broke all of my
tunes (I have about 150 of them since I do a big lilypond project).

The problem: \score { << \new Voice="foo" \relative { c d e f g } >> }

produces different outputs in the two versions. because I do not specify an
absolute note in the '\relative' syntax the first note inside the score is
supposed to be taken as absolute and therefore it is supposed to be middle c.
In lilypond 2.16 this is the case.
In lilypond 2.18 this is not the case. The first c in this example is drawn
as the c below middle c. I really don't know why.

I really don't care what the default of lilypond behavior as far as
\relative without a note outside the score is as long as it stays the same
across versions of lilypond. I now have to manually edit 150 files...:(

Trying to compile on 2.18.2 with \version "2.16.2" did not help me as I did
not get 2.16 behavior.

Hope this helps and I did not come off sounding harsh. I love lilypond
greatly, its just that I'm pissed at having to edit 150 files and I'm
wondering if I'll have to do this again in a half a year or a year...:)

Mark


_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user

--
Matthias Böhringer
Brunnenstraße 6
72296 Schopfloch-Unteriflingen