>> To sum up: Keywords like `orientation' are far too frequent in
>> normal text to be handled without protection if convert-ly is
>> applied to lilypond-book (or texinfo) input.
>
> I'm fine with this being a command-line option to convert-ly.
> Actually, this could even be the default -- as long
On Thu, Oct 21, 2010 at 6:06 AM, Werner LEMBERG wrote:
>
> What I consider problematic is that syntax changes aren't restricted to
> lilypond
> environments.
This is useful for updating the docs -- we *want* it to change text
like "to change the direction of the slur, use \oldSlurUpCommand".
>
In the documentation, there is an example how to convert a texinfo
file to a newer version:
convert-ly --from=... --to=... --no-version *.itely
A similar command can be used for lilypond-book input files:
convert-ly --from=... --to=... --no-version *.tex
What I consider problematic is that
