[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Converting a large project from 2.18 to 2.19: what to expect?
From: |
David Kastrup |
Subject: |
Re: Converting a large project from 2.18 to 2.19: what to expect? |
Date: |
Wed, 05 Apr 2017 10:20:17 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
Malte Meyn <address@hidden> writes:
> Output changes: MIDI articulation, MultiMeasureRest spacing, whiteout style.
>
> Input changes: the omission of “parser” and “location” arguments in
> music functions,
convert-ly takes a good stab at that, and even then it's optional.
I really think that convert-ly should have most of the bases covered:
moving from 2.18 to current 2.19 should be mostly painless.
> \partial at volta repeats and time signature changes.
Well, yes. But mostly you had to fiddle with manual workarounds
previously, and most of those workarounds are no longer necessary but
will not cause damage either.
> These are only some examples. For details and other changes see
> http://lilypond.org/doc/v2.19/Documentation/changes/
--
David Kastrup
Re: Converting a large project from 2.18 to 2.19: what to expect?, Andrew Bernard, 2017/04/05