summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJames Lowe <pkx166h@gmail.com>2014-09-27 15:55:31 +0100
committerJames Lowe <pkx166h@gmail.com>2014-10-02 08:30:10 +0100
commitf6c7a2188e3904475fc46818742d01d50034a159 (patch)
tree508e1298890ff8acc143d71008ba254f12d44eec
parentb512137cb2a89c9b5f880fc089221805491c9bdf (diff)
Doc: Usage: Add more explanation for LaTeX environ
Issue 4136 Taken from: http://lists.gnu.org/archive/html/bug-lilypond/2014-08/msg00047.html Added paragraph explaining the finer details on how LaTeX handles environments using \begin{lilypond} ... \end{lilypond}
-rw-r--r--Documentation/usage/lilypond-book.itely28
1 files changed, 22 insertions, 6 deletions
diff --git a/Documentation/usage/lilypond-book.itely b/Documentation/usage/lilypond-book.itely
index c14c49b43b..4707d7083c 100644
--- a/Documentation/usage/lilypond-book.itely
+++ b/Documentation/usage/lilypond-book.itely
@@ -882,7 +882,7 @@ way you use, you can easily convert between PostScript and PDF with
tools, like @command{ps2pdf} and @command{pdf2ps} included in
Ghostscript package.
-To produce a PDF file through PDF@LaTeX{}, use
+To produce a PDF file through PDF@LaTeX{}, use;
@example
lilypond-book --pdf yourfile.lytex
@@ -893,8 +893,7 @@ pdflatex yourfile.tex
@cindex type1 fonts
@cindex dvips
@cindex invoking dvips
-To produce PDF output via @LaTeX{}/@command{dvips}/@command{ps2pdf}, you
-should do
+To produce PDF output via @LaTeX{}/@command{dvips}/@command{ps2pdf};
@example
lilypond-book yourfile.lytex
@@ -904,16 +903,33 @@ ps2pdf yourfile.ps
@end example
@noindent
-The @file{.dvi} file created by this process will not contain
- note heads. This is normal; if you follow the instructions, they
-will be included in the @file{.ps} and @file{.pdf} files.
+The @file{.dvi} file created by this process will not contain note heads.
+This is normal; if you follow the instructions, they will be included in
+the @file{.ps} and @file{.pdf} files.
Running @command{dvips} may produce some warnings about fonts; these
are harmless and may be ignored. If you are running @command{latex} in
twocolumn mode, remember to add @option{-t landscape} to the
@command{dvips} options.
+Environments such as;
+
+@example
+\begin@{lilypond@} @dots{} \end@{lilypond@}
+@end example
+
+@noindent
+are not interpreted by @LaTeX{}. Instead, @code{lilypond-book} extracts
+those @q{environments} into files of its own and runs LilyPond on them'.
+It then takes the resulting graphics and creates a @file{.tex} file
+where the @code{\begin@{lilypond@}}@dots{}@code{\end@{lilypond@}} macros
+are then replaced by @q{graphics inclusion} commands. It is at this
+time that @LaTeX{} is run (although @LaTeX{} will have run previously,
+it will have been, effectively, on an @q{empty} document in order to
+calculate things like @code{\linewidth}.
+
@knownissues
+
The @code{\pageBreak} command will not work within a
@code{\begin@{lilypond@} @dots{} \end@{lilypond@}} environment.