7 Convert-ly sequentially applies different conversions to upgrade a
8 Lilypond input file. It uses @code{\version} statements in the file to
9 detect the old version number.
11 @unnumberedsubsec Invoking convert-ly
14 convert-ly [OPTION]... [FILE]...
20 If version number cannot be determined, apply all conversions.
22 Do an inline edit of the input file. override @code{--output}
23 @item -f,--from=@var{from-patchlevel}
24 Set the level to convert from. If this is not set, convert-ly will
25 guess this, on the basis of @code{\version} strings in the file
26 @item -o,--output=@var{file}
27 Set the output file to write.
29 Normally, convert-ly adds a @code{\version} indicator
30 to the output. Specifying this option suppresses this.
33 Show all known conversions and exit
34 @item --to=@var{to-patchlevel}
35 Set the goal version of the conversion. It defaults to the latest
39 @unnumberedsubsec Example
41 Upgrade all lilypond files to 1.3.150:
43 convert-ly -e --to=1.3.150 `find -name '*.ly'`
46 @unnumberedsubsec Bugs
48 Not all language changes are handled. Multiple output options won't
51 @unnumberedsubsec Authors
53 @code{convert-ly} is written in @uref{http://www.python.org,Python}. It
54 was written by @email{hanwen@@cs.uu.nl, Han-Wen Nienhuys}. Report bugs
55 to @code{bug-gnu-music@@gnu.org}