Hi, I just ran convert-ly over an old score (typeset with v2.8.6) which contained the following line:
\override TextSpanner #'edge-text = #(cons (markup #:bigger #:bigger #:bigger #:upright "rit." ) "") Now the \bigger command was removed recently (replaced by \larger). A corresponding convert-ly rule does exist, but it explicitly checks for the backslash in front of the command. So the above line was left unchanged, which made lilypond choke. Should convert-ly rules be formulated so that Scheme-version of commands like the above are also taken into account? Which other commands does this affect? Max _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
