Use two spaces after a period; thanks Michael Rasmussen!

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

diff --git a/Documentation/user/chords.itely b/Documentation/user/chords.itely
index 63d5b2fb1ccb1af9cc03f8e0bebb6602a8465f9a..7fc6040f11018efa3cf59766dddd314ed2a2588c 100644 (file)
--- a/Documentation/user/chords.itely
+++ b/Documentation/user/chords.itely
@@ -1,16 +1,92 @@
 @c -*- coding: utf-8; mode: texinfo; -*-
+@ignore
+    Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
+
+    When revising a translation, copy the HEAD committish of the
+    version that you are working on.  See TRANSLATION for details.
+@end ignore
 
 
 @node Chords Blah
 @section Chords Blah
 
+Intro text.
+
 @menu
+* TODO chords fix::             
 @end menu
 
 
+@node TODO chords fix
+@subsection TODO chords fix
+
 @c  awkward name; awkward section name.
 @c  still, the Basic "chords" seems like a good name...  :(
-@anchor{Introducing chord names}
+@menu
+* A lead sheet::                
+* Introducing chord names::     
+* Chords mode::                 
+* Printing chord names::        
+@end menu
+
+@c really awkward; I just shoved this in here from the tutorial.
+@node A lead sheet
+@unnumberedsubsubsec A lead sheet
+
+@cindex Lead sheets
+@cindex chords
+@cindex chord names
+
+In popular music it is common to denote accompaniment with chord
+names.  Such chords can be entered like notes,
+
+@lilypond[verbatim,quote,ragged-right]
+\chordmode { c2 f4. g8 }
+@end lilypond
+
+Now each pitch is read as the root of a chord instead of a note.
+This mode is switched on with @code{\chordmode}.  Other chords can
+be created by adding modifiers after a colon.  The following
+example shows a few common modifiers:
+
+@lilypond[verbatim,quote,ragged-right]
+\chordmode { c2 f4:m g4:maj7 gis1:dim7 }
+@end lilypond
+
+For lead sheets, chords are not printed on staves, but as names on
+a line for themselves.  This is achieved by using @code{\chords}
+instead of @code{\chordmode}.  This uses the same syntax as
+@code{\chordmode}, but renders the notes in a @code{ChordNames}
+context, with the following result:
+
+@lilypond[verbatim,quote,ragged-right]
+\chords { c2 f4.:m g4.:maj7 gis8:dim7 }
+@end lilypond
+
+@cindex lead sheet
+When put together, chord names, lyrics and a melody form a lead
+sheet,
+
+@lilypond[verbatim,quote,ragged-right]
+<<
+  \chords { c2 g:sus4 f e }
+  \relative c'' {
+    a4 e c8 e r4
+    b2 c4( d)
+  }
+  \addlyrics { One day this shall be free __ }
+>>
+@end lilypond
+
+
+@seealso
+@quotation
+A complete list of modifiers and other options for layout can be
+found in @ruser{Chords}.
+@end quotation
+
+
+@node Introducing chord names
 @unnumberedsubsubsec Introducing chord names
 @cindex chord names
 
@@ -46,7 +122,7 @@ Note that the duration of chords must be specified outside the
 @end example
 
 
-@anchor{Chords mode}
+@node Chords mode
 @unnumberedsubsubsec Chords mode
 @cindex Chords mode
 
@@ -182,7 +258,7 @@ last
 @end lilypond
 
 
-@anchor{Printing chord names}
+@node Printing chord names
 @unnumberedsubsubsec Printing chord names
 
 @cindex printing chord names
@@ -313,8 +389,8 @@ base can be printed in lower case.
 @funindex chordPrefixSpacer
 @item chordPrefixSpacer
 The @q{m} for minor chords is usually printed right after the root of
-the chord. By setting @code{chordPrefixSpacer}, you can fix a spacer
-between the root and @q{m}. The spacer is not used when the root
+the chord.  By setting @code{chordPrefixSpacer}, you can fix a spacer
+between the root and @q{m}.  The spacer is not used when the root
 is altered.
 
 @end table
@@ -368,7 +444,3 @@ may result in strange chord names when chords are entered with the
 @code{< .. >} syntax.
 
 
-
-
-
-