Am 01.11.2017 um 09:26 schrieb David Kastrup:
I see that
commit 589ba7953e92ad4ad793d89291b97d738614408e
Author: Reinhold Kainhofer <reinh...@kainhofer.com>
Date: Sat Jun 28 14:07:25 2008 +0200
New function: \ottava #oct, replaces #(set-octavation oct)
was introduced in 2.11.53, _including_ the convert-ly rule.
However,
commit d00ca5c25ad78a6de4ed5098673bb151707f28c1
[…]
removed set-octavation in version 2.13.29 . So set-octavation seems
more like a backward compatibility remnant than anything else in 2.12.0.
I don't see that we can do this significantly better than it is
currently done.
One could have the same convert-ly rule twice: First time for the
version where a new feature is introduced and it’s *possible and
recommended* to use it. Second time for the version where the old
feature (and thus backward compatibility) is removed and you *have to*
use it.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
