+2004-11-13 Graham Percival <gperlist@shaw.ca>
+
+ * Documentation/user/lilypond-book.itely: add small warning about
+ noindent default in lilypond-book.
+
+ * Documentation/user/converters.itely: add examples for convert-ly.
+
2004-11-12 Karl Hammar <karl@aspodata.se>
* GNUmakefile.in (local-WWW-post): `find ...` overflows the
syntax changes between LilyPond versions.
It uses @code{\version} statements in the input files to detect the old
-version number. For example, to upgrade all LilyPond files in the
-current directory and its subdirectories, enter the following on the
-command line.
+version number. In most cases, to upgrade your input file it is sufficient
+to run
@example
-convert-ly -e `find . -name '*.ly' -print`
+covert-ly -e MYFILE.ly
+@end example
+
+If there are no changes to MYFILE.ly and if a file called MYFILE.ly.NEW
+is created, then MYFILE.ly is already updated.
+
+To upgrade LilyPond fragments in texinfo files, use
+
+@example
+convert-ly --from=... --to=... --no-version *.itely
@end example
In general, the program is invoked as follows:
@item indent=@var{size}\@var{unit}
sets indentation of the first music system to @var{size},
where @var{unit} = cm, mm, in, or pt. This option affects LilyPond,
-not the text layout. For single-line fragments, the default is to
-use no indentation.
+not the text layout. The default is to use no indentation.
For example
@example