* Documentation/user/basic-notation.itely (Ties): add tieDashed.

[lilypond.git] / Documentation / user / lilypond-book.itely

diff --git a/Documentation/user/lilypond-book.itely b/Documentation/user/lilypond-book.itely
index 09544f6c1f259eb4542d2e473274d797f6e286a8..2aa6b304ee72e35de6ebb810307c7092a37a684d 100644 (file)
--- a/Documentation/user/lilypond-book.itely
+++ b/Documentation/user/lilypond-book.itely
@@ -93,7 +93,7 @@ Under Unix, you can view the results as follows
 @example
 cd input/tutorial
 mkdir -p out/
-lilypond-book --output=out --psfonts=psfonts lilybook.tex
+lilypond-book --output=out --psfonts lilybook.tex
 @emph{lilypond-book (GNU LilyPond) 2.6.0}
 @emph{Reading lilybook.tex...}
 @emph{..lots of stuff deleted..}
@@ -107,7 +107,7 @@ xdvi lilybook
 To convert the file into a PDF document, run the following commands
 
 @example
-dvips -Ppdf -h psfonts lilybook
+dvips -Ppdf -h lilybook.psfonts lilybook
 ps2pdf lilybook.ps
 @end example
 
@@ -116,6 +116,9 @@ temporary files, which would clutter up the working directory.  To
 remedy this, use the @code{--output=@var{dir}} option.  It will create
 the files in a separate subdirectory @file{dir}.
 
+Running dvips will produce many warnings about fonts.  They are not
+harmful; please ignore them.
+
 Finally the result of the La@TeX{} example shown above.@footnote{This
 tutorial is processed with Texinfo, so the example gives slightly
 different results in layout.}  This finishes the tutorial section.
@@ -285,14 +288,16 @@ a PostScript file, add the following options to the @command{dvips}
 command line:
 
 @example
--Ppdf -h psfonts
+-Ppdf -h @var{file}.psfonts
 @end example
 
 @noindent
-where the @command{psfonts} file is obtained from
+where the @var{file}@command{psfonts} file is obtained from
 @command{lilypond-book}, @xref{Invoking lilypond-book} for details. PDF
-can then be produced with a PostScript to PDF translator like 
-@code{ps2pdf} (which is part of GhostScript).
+can then be produced with a PostScript to PDF translator like
+@code{ps2pdf} (which is part of GhostScript).  Running @command{dvips}
+will produce some warnings about fonts; these are harmless and may
+be ignored.
 
 @cindex international characters
 @cindex latin1
@@ -567,9 +572,9 @@ To produce PDF output from the lilypond-book file (here called
 @code{yourfile.lytex}), you should do
 
 @example
-lilypond-book --psfonts=tempfonts.ps yourfile.lytex
+lilypond-book --psfonts yourfile.lytex
 latex yourfile.tex
-dvips -h tempfonts.ps -Ppdf yourfile.dvi
+dvips -h yourfile.psfonts -Ppdf yourfile.dvi
 ps2pdf yourfile.ps
 @end example
 
@@ -639,9 +644,9 @@ Process LilyPond snippets using @var{command}.  The default command is
 @code{lilypond}.  @code{lilypond-book} will not --filter and --process
 at the same time.
 
-@itemx --psfonts=FILE
-extract all PostScript fonts into FILE for LaTeX.  This is necessary
-for @command{dvips -h FILE}.
+@itemx --psfonts
+extract all PostScript fonts into @file{@var{file}.psfonts} for dvips.
+This is necessary for @command{dvips -h @var{file}.psfonts}.
 
 @item -V
 @itemx --verbose
@@ -660,11 +665,6 @@ are ignored.
 
 Only the first @code{\score} of a LilyPond block is processed.
 
-@c CHECKME--FIXME
-The size of a music block is limited to 1.5 KB, due to technical
-problems with the Python regular expression engine.  For longer files,
-use @code{\lilypondfile}.
-
 
 @node Filename extensions
 @section Filename extensions