Merge branch 'master' of ssh://jomand@git.sv.gnu.org/srv/git/lilypond

[lilypond.git] / Documentation / user / non-music.itely

diff --git a/Documentation/user/non-music.itely b/Documentation/user/non-music.itely
index db77f49497e851f318e07d525286d910b8e6c1be..635c070af582e8031ea5a1e6149a007007ceac3e 100644 (file)
--- a/Documentation/user/non-music.itely
+++ b/Documentation/user/non-music.itely
@@ -7,6 +7,8 @@
     version that you are working on.  See TRANSLATION for details.
 @end ignore
 
     version that you are working on.  See TRANSLATION for details.
 @end ignore
 

+@c \version "2.11.38"
+

 @c A menu is needed before every deeper *section nesting of @node's; run
 @c     M-x texinfo-all-menus-update
 @c to automatically fill in these menus before saving changes
 @c A menu is needed before every deeper *section nesting of @node's; run
 @c     M-x texinfo-all-menus-update
 @c to automatically fill in these menus before saving changes


@@ -14,7 +16,7 @@
 @node Non-musical notation
 @chapter Non-musical notation
 
 @node Non-musical notation
 @chapter Non-musical notation
 

-This section deals with general lilypond issues, rather than
+This section deals with general LilyPond issues, rather than

 specific notation.
 
 @menu
 specific notation.
 
 @menu


@@ -111,7 +113,7 @@ Centered at the bottom of the last page.
 @end table
 
 Here is a demonstration of the fields available.  Note that you
 @end table
 
 Here is a demonstration of the fields available.  Note that you

-may use any @ref{Text markup}, commands in the header.
+may use any @ref{Formatting text}, commands in the header.

 
 @lilypond[quote,verbatim,line-width=11.0\cm]
 \paper {
 
 @lilypond[quote,verbatim,line-width=11.0\cm]
 \paper {


@@ -292,7 +294,7 @@ composer flush right on a single line.
 
 A particular place of a score can be marked using the @code{\label}
 command, either at top-level or inside music.  This label can then be
 
 A particular place of a score can be marked using the @code{\label}
 command, either at top-level or inside music.  This label can then be

-refered to in a markup, to get the number of the page where the marked
+referred to in a markup, to get the number of the page where the marked

 point is placed, using the @code{\page-ref} markup command.
 
 @lilypond[verbatim,line-width=11.0\cm]
 point is placed, using the @code{\page-ref} markup command.
 
 @lilypond[verbatim,line-width=11.0\cm]


@@ -322,14 +324,14 @@ is not known;
 @end enumerate
 
 The reason why a gauge is needed is that, at the time markups are
 @end enumerate
 
 The reason why a gauge is needed is that, at the time markups are

-interpreted, the page breaking has not yet occured, so the page numbers
+interpreted, the page breaking has not yet occurred, so the page numbers

 are not yet known.  To work around this issue, the actual markup
 interpretation is delayed to a later time; however, the dimensions of
 the markup have to be known before, so a gauge is used to decide these
 dimensions.  If the book has between 10 and 99 pages, it may be "00",
 ie. a two digit number.
 
 are not yet known.  To work around this issue, the actual markup
 interpretation is delayed to a later time; however, the dimensions of
 the markup have to be known before, so a gauge is used to decide these
 dimensions.  If the book has between 10 and 99 pages, it may be "00",
 ie. a two digit number.
 

-@refcommands
+@predefined

 
 @funindex \label
 @code{\label}
 
 @funindex \label
 @code{\label}


@@ -377,14 +379,14 @@ number.  These variables may be changed by the user:
     \fill-line { \null "Table des matières" \null }
     \hspace #1
   }
     \fill-line { \null "Table des matières" \null }
     \hspace #1
   }

-  %% use larfer font size
+  %% use larger font size

   tocItemMarkup = \markup \large \fill-line {
     \fromproperty #'toc:text \fromproperty #'toc:page
   }
 }
 @end verbatim
 
   tocItemMarkup = \markup \large \fill-line {
     \fromproperty #'toc:text \fromproperty #'toc:page
   }
 }
 @end verbatim
 

-Note how the toc element text and page number are refered to in
+Note how the toc element text and page number are referred to in

 the @code{tocItemMarkup} definition.
 
 New commands and markups may also be defined to build more elaborated
 the @code{tocItemMarkup} definition.
 
 New commands and markups may also be defined to build more elaborated


@@ -442,7 +444,7 @@ tocAct =
 
 Init files: @file{ly/@/toc@/-init@/.ly}.
 
 
 Init files: @file{ly/@/toc@/-init@/.ly}.
 

-@refcommands
+@predefined

 
 @funindex \table-of-contents
 @code{\table-of-contents}
 
 @funindex \table-of-contents
 @code{\table-of-contents}


@@ -466,7 +468,7 @@ what was entered.  This is convenient for checking the music; octaves
 that are off or accidentals that were mistyped stand out very much
 when listening to the MIDI output.
 
 that are off or accidentals that were mistyped stand out very much
 when listening to the MIDI output.
 

-@refbugs
+@knownissues

 
 Many musically interesting effects, such as swing, articulation,
 slurring, etc., are not translated to midi.
 
 Many musically interesting effects, such as swing, articulation,
 slurring, etc., are not translated to midi.


@@ -564,7 +566,7 @@ in the @code{\midi@{@}} section.
 @end example
 
 
 @end example
 
 

-@refbugs
+@knownissues

 
 Unterminated (de)crescendos will not render properly in the midi file,
 resulting in silent passages of music.  The workaround is to explicitly
 
 Unterminated (de)crescendos will not render properly in the midi file,
 resulting in silent passages of music.  The workaround is to explicitly


@@ -643,7 +645,7 @@ instrument is used.
 @end menu
 
 @node Repeats and MIDI
 @end menu
 
 @node Repeats and MIDI

-@unnumberedsubsubsec Repeats and MIDI
+@subsubsection Repeats and MIDI

 
 @cindex expanding repeats
 @funindex \unfoldRepeats
 
 @cindex expanding repeats
 @funindex \unfoldRepeats