[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 1350 in lilypond: make convert-ly restrict to `lilypond' enviromen
From: |
lilypond |
Subject: |
Issue 1350 in lilypond: make convert-ly restrict to `lilypond' enviroments |
Date: |
Thu, 21 Oct 2010 05:43:39 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Enhancement
New issue 1350 by lemzwerg: make convert-ly restrict to `lilypond'
enviroments
http://code.google.com/p/lilypond/issues/detail?id=1350
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 syntax changes aren't restricted to
lilypond
environments. Just consider this input:
\version "2.11.50"
orientation
If you say
convert-ly --to=2.11.51 test.ly > /dev/null
You get this output:
convert-ly (GNU LilyPond) 2.13.31
Processing `test.ly'...
Applying conversion: 2.11.23, 2.11.35, 2.11.38, 2.11.46, 2.11.48, 2.11.50,
Not smart enough to convert orientation in fret-diagram properties. Use
fret-diagram-details.
2.11.51
which can be quite irritating. Fortunately, no action is taken upon,
but this is just accidentally true.
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.
- Issue 1350 in lilypond: make convert-ly restrict to `lilypond' enviroments,
lilypond <=