release: 1.4.2

[lilypond.git] / Documentation / user / converters.itely

diff --git a/Documentation/user/converters.itely b/Documentation/user/converters.itely
index 945f4f15d224e0b5de57e75d921c915f9b288034..71f53b947d449becea93c0fe9627b753a58e9be4 100644 (file)
--- a/Documentation/user/converters.itely
+++ b/Documentation/user/converters.itely
@@ -26,8 +26,8 @@ to import files from a program that has no converter for its native
 format.
 
 It is possible to record a MIDI file using a digital keyboard, and then
-convert it to @file{.ly}. However, human players can not rhythmically
-exact enough to make a MIDI to .ly conversion trivial.  midi2ly tries to
+convert it to @file{.ly}. However, human players are not rhythmically
+exact enough to make a MIDI to LY conversion trivial.  midi2ly tries to
 compensate for these timing errors, but is not very good at this. It is
 therefore not recommended to use midi2ly for human-generated midi
 files. Correcting the quantization mistakes of the human player takes a
@@ -39,7 +39,7 @@ robust midi2ly.
 @subsection Invoking midi2ly
 
 @example
-        midi2ly [OPTION]... MIDI-FLIE
+        midi2ly [@var{OPTION}]@dots{} @var{MIDI-FILE}
 @end example
 
 @unnumberedsubsec Options
@@ -93,7 +93,7 @@ file to a ready-to-use LilyPond file.
 Usage:
 
 @example
-        etf2ly [OPTION]... ETF-FILE
+        etf2ly [@var{OPTION}]@dots{} @var{ETF-FILE}
 @end example
 
 Convert ETF to LilyPond.
@@ -112,11 +112,9 @@ version information
 @refbugs
 
 Known: articulation scripts are buggy.  Empty measures confuse etf2ly.
-Report bugs to @email{bug-gnu-music@@gnu.org}.
 
 Written by @email{Han-Wen Nienhuys,hanwen@@cs.uu.nl}.
 
-
 Report bugs to @email{bug-gnu-music@@gnu.org}.
 
 @node abc2ly
@@ -128,11 +126,30 @@ ABC is a fairly simple ASCII based format. It is described at
 @subsection Invoking abc2ly
 
 @example
-        abc2ly [OPTION]... ABC-FILE
+        abc2ly [@var{OPTION}]@dots{} @var{ABC-FILE}
 @end example
 
 Convert ABC to LilyPond.
 
+There is a rudimentary facility for adding lilypond code to the ABC
+source file.  If you say:
+
+@example
+        %%LY voices \property Voice.noAutoBeaming=##t
+@end example
+
+This will cause the text following the keyword ``voices'' to be inserted 
+into the current voice of the lilypond output file.
+
+Similarly:
+
+@example
+        %%LY slyrics more words
+@end example
+
+will cause the text following the ``slyrics'' keyword to be inserted
+into the current line of lyrics.
+
 @unnumberedsubsec Options
 @table @code
 @item   -h,--help
@@ -148,9 +165,15 @@ version information
 The ABC standard is not very "standard". For extended features
 (eg. polyphonic music) different conventions exist. 
 
+Multiple tunes in one file cannot be converted.
 
-Written by @email{Han-Wen Nienhuys,hanwen@@cs.uu.nl}.
+ABC synchronizes words and notes at the beginning of a line; abc2ly does 
+not.
+
+abc2ly ignores the ABC beaming.
 
+Written by @email{Han-Wen Nienhuys,hanwen@@cs.uu.nl}.
+@c How about Laura?   /MB
 
 Report bugs to @email{bug-gnu-music@@gnu.org}.
 
@@ -165,7 +188,7 @@ Report bugs to @email{bug-gnu-music@@gnu.org}.
 @subsection Invoking pmx2ly
 
 @example
-        pmx2ly [OPTION]... PMX-FILE
+        pmx2ly [@var{OPTION}]@dots{} @var{PMX-FILE}
 @end example
 
 Convert PMX to LilyPond.
@@ -200,7 +223,7 @@ include a @code{\header} field if a @file{.ref} file is supplied
 @subsection Invoking musedata2ly
 
 @example
-        musedata2ly [OPTION]... MUSEDATA-FILE
+        musedata2ly [@var{OPTION}]@dots{} @var{MUSEDATA-FILE}
 @end example
 
 Convert Musedata to LilyPond.
@@ -234,7 +257,7 @@ convert part of a Mup file to a ready-to-use LilyPond file.
 @subsection Invoking mup2ly
 
 @example
-        mup2ly [OPTION]... MUP-FILE
+        mup2ly [@var{OPTION}]@dots{} @var{MUP-FILE}
 @end example
 
 Convert Mup to LilyPond.
@@ -255,7 +278,7 @@ write output to @var{FILE}
 @item  -v,--version
 version information
 @item  -w,--warranty
-print warranty and copyright.  Mup2ly comes with absolutlely @strong{NO WARRANTY}.
+print warranty and copyright.  Mup2ly comes with absolutely @strong{NO WARRANTY}.
 @end table