+@c -*-texinfo-*-
+
@node convert-ly
@chapter convert-ly
-@code{convert-ly} sequentially applies different
-lilypond-conversions to upgrade a Lilypond input file. It uses
-@code{\version} statements in the file to detect the old version
-number.
+Convert-ly sequentially applies different conversions to upgrade a
+Lilypond input file. It uses @code{\version} statements in the file to
+detect the old version number.
+
+@subsection Invoking convert-ly
@example
- convert-ly [options] [files]
+ convert-ly [OPTION]... [FILE]...
@end example
-@section Options
-@table @samp
-@item --output
- The output file to write.
-@item --edit
+
+@table @code
+@item -a,--assume-old
+ If version number cannot be determined, apply all conversions.
+@item -e,--edit
Do an inline edit of the input file. override @code{--output}
-@item --show-rules
- shows all known conversions, and exit
-@item --from=@var{FROM_PATCHLEVEL}
+@item -f,--from=@var{FROM_PATCHLEVEL}
Set the level to convert from. If this is not set, convert-ly will
guess this, on the basis of @code{\version} strings in the file
+@item -o,--output
+ The output file to write.
+@item -n,--no-version
+ Normally, convert-ly adds a @code{\version} indicator
+to the output. Specifying this option suppresses this.
+
+@item --show-rules
+ shows all known conversions, and exit
@item --to=@var{TO_PATCHLEVEL}
Set the goal version of the conversion. It defaults to the latest
available version.
Not all language changes are handled. Multiple output options won't
work.
-convert-ly is written in python, so you have install
-@uref{http://www.python.org,python}. It was written by
-@email{hanwen@@cs.uu.nl, Han-Wen Nienhuys}.
+@code{convert-ly} is written in @uref{http://www.python.org,Python}. It
+was written by @email{hanwen@@cs.uu.nl, Han-Wen Nienhuys}. Report bugs
+to @code{bug-gnu-music@@gnu.org}