2013/9/22 Joachim Mairböck <[email protected]> > 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). > > Hi Joachim
the \version statement is useful for convert-ly to update to the new syntax. But convert-ly can only upgrade the syntax; downgrade is not possible. This has been recently added explicitely in the documentation of 2.17.27 (to be released in the next days): https://code.google.com/p/lilypond/issues/detail?id=3477 So if you have this file: \version "2.16.2" { \tempo 4 = 40 ~ 46 c4. e8 a4 g b,2 d4 r } you can run convert-ly in order to use it with the latest development version. But once you've update to the new syntax, you cannot go back to the older syntax. You should use a control version system like Git or Mercurial for this sort of stuff. Hope it helps Federico _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
