lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Converting from 1.4.12 to 2.10.33


From: Joseph Haig
Subject: Converting from 1.4.12 to 2.10.33
Date: Tue, 29 Apr 2008 13:16:30 +0100

I downloaded a Lilypond 1.4.12 file from
http://www.upv.es/coro/victoria/partituras.html and run it through
convert-ly, which, gave the following output (in addition to the
output file):

convert-ly (GNU LilyPond) 2.10.33
Processing `old/Ascendens_Christus_In_Altum-1-Kyrie.ly'...
Applying conversion: 1.5.33, 1.5.38, 1.5.40, 1.5.49, 1.5.52, 1.5.56,
1.5.58, 1.5.59, 1.5.62, 1.5.67, 1.5.68, 1.5.71, 1.5.72, 1.6.5, 1.7.1,
1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.10, 1.7.11, 1.7.13, 1.7.15,
1.7.16, 1.7.17, 1.7.18, 1.7.19, 1.7.22, 1.7.23, 1.7.24, 1.7.28, 1.9.0,
1.9.1, 1.9.2, 1.9.3, 1.9.4, 1.9.5, 1.9.6, 1.9.7, 1.9.8, 2.1.1, 2.1.2,
2.1.3, 2.1.4, 2.1.7, 2.1.10, 2.1.11, 2.1.12, 2.1.13, 2.1.14, 2.1.15,
2.1.16, 2.1.17, 2.1.18, 2.1.19, 2.1.20, 2.1.21, 2.1.22, 2.1.23,
2.1.24, 2.1.25, 2.1.26, 2.1.27, 2.1.28, 2.1.29, 2.1.30, 2.1.31,
2.1.33, 2.1.34, 2.1.36, 2.2.0, 2.3.1, 2.3.2,
Not smart enough to convert textheight
Please refer to the manual for details, and update manually.
Page layout has been changed, using paper size and margins.
textheight is no longer used.
2.3.4, 2.3.6, 2.3.8, 2.3.9, 2.3.10, 2.3.11, 2.3.12, 2.3.16, 2.3.17,
2.3.18, 2.3.22, 2.3.23, 2.3.24, 2.4.0, 2.5.0, 2.5.1, 2.5.2, 2.5.3,
2.5.12, 2.5.13, 2.5.17, 2.5.18, 2.5.21, 2.5.25, 2.6.0, 2.7.0, 2.7.1,
2.7.2, 2.7.4, 2.7.6, 2.7.10, 2.7.11, 2.7.12, 2.7.13, 2.7.14, 2.7.15,
2.7.22, 2.7.24, 2.7.28, 2.7.29, 2.7.30, 2.7.31, 2.7.32, 2.7.32,
2.7.36, 2.7.40, 2.9.4, 2.9.6, 2.9.9, 2.9.11, 2.9.13, 2.9.16, 2.9.19,
2.10.0, 2.10.10

There is a warning, but doesn't seem to be any indication of anything
seriously wrong.  However, running lilypond on the output file I get:

error: can't find music object: OldLyricCombineMusic

What would I need to tweak to get this working properly?  Or is 1.4.12
just so old that it is not worth converting?

Thanks,

Joe




reply via email to

[Prev in Thread] Current Thread [Next in Thread]