Joachim Mairböck <j.mairbo...@gmail.com> writes: > The syntax of a ranged tempo specification changed from \tempo <dur> = <low> > ~ <high> to \tempo <dur> = <low> - <high> from version 2.16 to current > unstable, i.e. it uses a '-' instead of a '~'. > > This is a good change. However, a source file containing a statement > like this and \version "2.16.0" doesn't compile using the current > unstable version. The \version command should enable compatibility > with older versions (and Lilypond should accept both forms if such a > \version statement exists).
In an ideal world, this would be how things work. But in practice, LilyPond is complex enough that it can only support one syntax at a time. The \version header is not useless: we provide a tool convert-ly that can be used for upgrading the syntax of a .ly file to the version currently supported by your installed version of LilyPond. The conversion is one-way, though: once you upgraded the syntax, you can't downgrade it again. <URL:http:http://lilypond.org/doc/v2.17/Documentation/usage/updating-files-with-convert_002dly> -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
