Alex,
On Tue, 31 Oct 2017 22:35:59 +0100, Alex Schreiber <alex4...@gmx.de> wrote:
> A file with content
>
> {c''' #(set-octavation 1) c''' #(set-octavation 0) c'''}
>
> compiles just fine in lilypond 2.12.0, but not in lilypond 2.18.2. However,
>
> convert-ly --from=2.12.0 --to=2.18.2 file.ly
>
> does not change anything.
> It seems as if
>
> @rule ((2, 11, 55), "#(set-octavation oct) -> \\ottava #oct
>
> in python/convertrules.py does not contain the correct version number.
>
>
What is the command you are running?
If you do not '>' the command to a new file then all you will see is the
conversion done on screen.
E.g.:
--snip--
james@james-OptiPlex-990:~/Desktop$ convert-ly --from=2.12.0 --to=2.19.0
untitled.ly
convert-ly (GNU LilyPond) 2.21.0
convert-ly: Processing `untitled.ly'...
Applying conversion: 2.12.3, 2.13.0, 2.13.1, 2.13.4, 2.13.10, 2.13.16, 2.13.18,
2.13.20, 2.13.27, 2.13.29, 2.13.31, 2.13.36, 2.13.39, 2.13.40, 2.13.42,
2.13.44, 2.13.46, 2.13.48, 2.13.51, 2.14.0, 2.15.7, 2.15.9, 2.15.10, 2.15.16,
2.15.17, 2.15.18, 2.15.19, 2.15.20, 2.15.25, 2.15.32, 2.15.39, 2.15.40,
2.15.42, 2.15.43, 2.16.0, 2.17.0, 2.17.4, 2.17.5, 2.17.6, 2.17.11, 2.17.14,
2.17.15, 2.17.18, 2.17.19, 2.17.20, 2.17.25, 2.17.27, 2.17.29, 2.17.97, 2.18.0
\version "2.18.0"
{c''' #(set-octavation 1) c''' #(set-octavation 0) c'''}
{a b c}
---snip--
and the file does NOT contain the new version number.
If add '> mynewfilename.ly' to the above commen
then my new file (mynewfilename.ly) does get the new version number and the
original stays intact.
If you want to edit in place then use the '-e' switch (run convert-ly --help
for more options or look in the online documentation for help).
However, if I have misunderstood, then let us know and include some output.
Regards
James
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
