Change Info docs setup and clean up Documentation/user/GNUmakefile

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

diff --git a/Documentation/user/fundamental.itely b/Documentation/user/fundamental.itely
index 88866e26751bb494f67256b340e29c8d6851ea61..1e56b0e4f250f3d2d11292d75891b65d8fdbf93f 100644 (file)
--- a/Documentation/user/fundamental.itely
+++ b/Documentation/user/fundamental.itely
@@ -131,9 +131,13 @@ MIDI output respectively.  They are described fully in the
 Notation Reference -- @ruser{Score layout} and
 @ruser{Creating MIDI files}.
 
 Notation Reference -- @ruser{Score layout} and
 @ruser{Creating MIDI files}.
 

-The @code{\book} command allows
-several @code{\score} blocks to be combined into one output.
-If there are several @code{\book} blocks each one produces a
+You may code multiple @code{\score} blocks.  Each will be
+treated as a separate score, but they will be all combined into
+a single output file.  A @code{\book} command is not necessary
+-- one will be implicitly created.  However, if you would like
+separate output files from one @code{.ly} file then the
+@code{\book} command should be used to separate the different
+sections: each @code{\book} block will produce a

 separate output file.  For details see @ruser{Multiple scores
 in a book}.
 
 separate output file.  For details see @ruser{Multiple scores
 in a book}.
 


@@ -1191,7 +1195,7 @@ For example: a @code{Staff} context can contain many
 contain many @code{Staff} contexts.
 
 @quotation
 contain many @code{Staff} contexts.
 
 @quotation

-@image{context-example,5cm,,}
+@sourceimage{context-example,5cm,,}

 @end quotation
 
 Each context has the responsibility for enforcing some notation rules,
 @end quotation
 
 Each context has the responsibility for enforcing some notation rules,


@@ -1585,7 +1589,7 @@ engraver is removed from a context it can no longer produce its
 output.  This is a crude way of modifying the output, but it
 can sometimes be useful.
 
 output.  This is a crude way of modifying the output, but it
 can sometimes be useful.
 

-@unnumberedsubsubsec Changing a single context
+@subsubsection Changing a single context

 
 To remove an engraver from a single context we use the
 @code{\with} command placed immediately after the context creation 
 
 To remove an engraver from a single context we use the
 @code{\with} command placed immediately after the context creation 


@@ -1666,7 +1670,7 @@ the notes in all the voices on that staff:
 >>
 @end lilypond
 
 >>
 @end lilypond
 

-@unnumberedsubsubsec Changing all contexts of the same type
+@subsubsection Changing all contexts of the same type

 
 The examples above show how to remove or add engravers to
 individual contexts.  It is also possible to remove or add 
 
 The examples above show how to remove or add engravers to
 individual contexts.  It is also possible to remove or add 


@@ -1778,24 +1782,26 @@ melody = \relative c' @{
 @}
 @end example
 
 @}
 @end example
 

-We don't need two @code{\version} commands.  We'll need the @code{melody}
-section.  We don't want two @code{\score} sections -- if we had two
-@code{\score}s, we'd get the two parts separately.  We want them together,
-as a duet.  Within the @code{\score} section, we don't need two
-@code{\layout} or @code{\midi}.
-
-If we simply cut and paste the @code{melody} section, we would end up with
-two @code{melody} sections.  So let's rename them.  We'll call the section
-for the soprano @code{sopranoMusic} and the section for the cello
-@code{celloMusic}.  While we're doing this, let's rename @code{text}
-to be @code{sopranoLyrics}.  Remember to rename both instances of all
-these names -- both the initial definition (the
+We don't need two @code{\version} commands.  We'll need the 
+@code{melody} section.  We don't want two @code{\score} sections
+-- if we had two @code{\score}s, we'd get the two parts separately.
+We want them together, as a duet.  Within the @code{\score} 
+section, we don't need two @code{\layout} or @code{\midi}.
+
+If we simply cut and paste the @code{melody} section, we would 
+end up with two @code{melody} definitions.  This would not generate
+an error, but the second one would be used for both melodies.
+So let's rename them to make them distinct.  We'll call the 
+section for the soprano @code{sopranoMusic} and the section for
+the cello @code{celloMusic}.  While we're doing this, let's rename
+@code{text} to be @code{sopranoLyrics}.  Remember to rename both
+instances of all these names -- both the initial definition (the

 @code{melody = \relative c' @{ } part) and the name's use (in the
 @code{\score} section).
 
 @code{melody = \relative c' @{ } part) and the name's use (in the
 @code{\score} section).
 

-While we're doing this, let's change the cello part's staff -- celli
-normally use bass clef.  We'll also give the cello some different
-notes.
+While we're doing this, let's change the cello part's staff -- 
+celli normally use bass clef.  We'll also give the cello some 
+different notes.

 
 @example
 \version "2.11.38"
 
 @example
 \version "2.11.38"


@@ -2347,3 +2353,4 @@ PedalOrganMusic = \relative c {
 
 
 
 
 
 

+