release: 1.3.122

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

diff --git a/Documentation/user/refman.itely b/Documentation/user/refman.itely
index b463a79c61af15188a163a3708552514facf3ccf..33a734826d0af7f8061ca7b7ddba927f4d82d1df 100644 (file)
--- a/Documentation/user/refman.itely
+++ b/Documentation/user/refman.itely
@@ -7,7 +7,8 @@
 @c - Fix indexing (keyindex) so it doesn't add line breaks  /MB
 
 @c ugh: because of @include, we need to fill in these nodes
-@node Reference Manual
+
+@node Reference Manual, , , top
 @chapter Reference Manual
 
 @menu
@@ -67,13 +68,9 @@ expressions into performances (MIDI) or graphics (eg. PostScript).
 can enter and edit them in manageable chunks.
 @end itemize
 
-
-
 @node Top level
 @section Top level
 
-@cindex top level
-
 This section describes what you may enter at top level.
 
 
@@ -112,6 +109,10 @@ It is customary to put the @code{\header} at the top of the file.
 @node Pitch names
 @section Pitch names
 
+@cindex pitch names
+@cindex note names
+@cindex chord modifier names
+
 Note names and chord modifiers can be customised for nationalities.
 languages and conventions.  The syntax is as follows.
 @example
@@ -121,17 +122,15 @@ languages and conventions.  The syntax is as follows.
 
 See @file{ly/nederlands.ly} and @file{ly/chord-modifiers.ly} for
 specific examples how to do this.  tables can be tailored specified
-using. Some national note names have been provided, see @ref{Other
-languages}.
-
+using. Some national note names have been provided, see
+@ref{Other languages}.
 A @code{\paper} block at top level sets the default paper block.  A
 @code{\midi} block at top level works similarly.
 
-
-
 Identifier assignments may appear at top level.  Semicolons are
 forbidden after top level assignments.
 
+@cindex assignments
 
 
 @node Lexical conventions
@@ -147,7 +146,6 @@ forbidden after top level assignments.
 
 @indexcode{%}
 
-
 A one line comment is introduced by a `@code{%}' character. 
 Block comments are started by `@code{%@{}' and ended by `@code{%@}}'. 
 They cannot be nested.
@@ -159,6 +157,10 @@ They cannot be nested.
 LilyPond contains a Scheme interpreter (the GUILE library) for
 internal use. The interpreter is accessed by the pound sign:
 
+@cindex Scheme
+@cindex GUILE
+@cindex Scheme, in-line code
+
 Whereever the syntax allows Scheme expressions, you may enter one as
 
 @example
@@ -265,11 +267,11 @@ Specify the version of LilyPond that a file was written for.  The
 argument is a version string in quotes, for example @code{"1.2.0"}. 
 This is used to detect invalid input, and to aid
 @code{convert-ly}, a tool that automatically upgrades input files.
-
+@cindex convert-ly
 
 @node Other languages
 @section Other languages
-@cindex Other languages
+@cindex Note names, international
 
 Note name definitions have been provided in various languages. 
 Simply include the language specific init file.  For example:
@@ -518,7 +520,9 @@ corresponding to C and 7 corresponding to B.  The shift is zero for a
 natural, negative to add flats, or positive to add sharps.
 
 In Note and Chord mode, pitches may be designated by names.  See
-section @ref{Other languages} for pitch names in different languages.
+section
+ @c @ref{Other languages} FIXME
+ for pitch names in different languages.
 
 The syntax for duration specification is
 
@@ -567,8 +571,6 @@ but both forms will be accepted.
 LilyPond has predefined sets of notenames for various languages.  See
 @ref{Other languages}.
 
-
-
 The optional octave specification takes the form of a series of
 single quote (`@code{'}@indexcode{'}') characters or a series of comma
 (`@code{,}@indexcode{,}') characters.  Each @code{'} raises the pitch by one
@@ -594,17 +596,15 @@ octave; each @code{,} lowers the pitch by an octave.
   ceses' eses' geses' ases' beses'
 @end lilypond
 
-Whenever a C-sharp is desired,  you must specify a C-sharp.  LilyPond
+Whenever a C-sharp is desired, you must specify a C-sharp.  LilyPond
 will determine what accidentals to typeset depending on the key and
-context.  A reminder accidental 
+context.  A reminder accidental
 @cindex reminder accidental
- can be
-forced by adding an exclamation mark `@code{!}' after the pitch.  A
-cautionary accidental, 
+can be forced by adding an exclamation mark `@code{!}' after the pitch.
+A cautionary accidental,
 @cindex cautionary accidental
- i.e., an
-accidental within parentheses can be obtained by adding the question
-mark `@code{?}@indexcode{?}' after the pitch.
+i.e., an accidental within parentheses can be obtained by adding the
+question mark `@code{?}@indexcode{?}' after the pitch.
 
 @lilypond[fragment,verbatim,center]
   cis' d' e' cis'  c'? d' e' c'!
@@ -982,11 +982,6 @@ warning message will appear and no ties will be created.
   e' ~ e' <c' e' g'> ~ <c' e' g'>
 @end lilypond
 
-
-
-[TODO: explain Requests]
-
-
 @cindex articulations
 
 @cindex scripts
@@ -1036,10 +1031,9 @@ In addition, it is possible to place arbitrary strings of text or
 @TeX{} above or below notes by using a string instead of an
 identifier: `@code{c^"text"}'.  Fingerings 
 @cindex fingering
- can be
-placed by simply using digits.  All of these note ornaments appear in
-the printed output but have no effect on the MIDI rendering of the
-music.
+can be placed by simply using digits.  All of these note ornaments
+appear in the printed output but have no effect on the MIDI rendering of
+the music.
 
 To save typing, fingering instructions (digits 0 to 9 are
 supported) and single characters shorthands exist for a few
@@ -1049,7 +1043,7 @@ common symbols
 
   \score {
     \notes {
-      \property Voice.textStyle = typewriter
+      \property Voice.TextScript \set #'font-style = #'typewriter
       c''4-._"c-."      s4
       c''4--_"c-{}-"    s4
       c''4-+_"c-+"      s4
@@ -1104,7 +1098,6 @@ c4-\textscript "foo" "normal"
 
 This is equivalent to `@code{c4-6 c4-"foo"}'.  
 
-
 @cindex scripts
 
 @example