GDP: NR 2 Reorganisation: Percussion headings

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

diff --git a/Documentation/user/input.itely b/Documentation/user/input.itely
index 9ad929c4af04164d44322f831cdec95a2bcb30fd..4ecad4b10537d24aa89da4fc0624c0320ba7a0c0 100644 (file)
--- a/Documentation/user/input.itely
+++ b/Documentation/user/input.itely
@@ -7,10 +7,12 @@
     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"
+

 @node Input syntax
 @chapter Input syntax
 
 @node Input syntax
 @chapter Input syntax
 

-This section deals with general lilypond input syntax issues,
+This section deals with general LilyPond input syntax issues,

 rather than specific notation.
 
 FIXME: don't complain about anything in this chapter.  It's still
 rather than specific notation.
 
 FIXME: don't complain about anything in this chapter.  It's still


@@ -305,7 +307,7 @@ It is possible to quote small fragments of a large score directly from
 the output.  This can be compared to clipping a piece of a paper score
 with scissors.
 
 the output.  This can be compared to clipping a piece of a paper score
 with scissors.
 

-This is done by definining the measures that need to be cut out
+This is done by defining the measures that need to be cut out

 separately.  For example, including the following definition
 
 
 separately.  For example, including the following definition
 
 


@@ -331,11 +333,7 @@ In order to use this feature, LilyPond must be invoked with
 @code{-dclip-systems}.  The clips are output as EPS files, and are
 converted to PDF and PNG if these formats are switched on as well.
 
 @code{-dclip-systems}.  The clips are output as EPS files, and are
 converted to PDF and PNG if these formats are switched on as well.
 

-For more information on output formats, see @rprogram{Invoking lilypond}.
-
-@seealso
-
-Examples: @c @lsr{non-notation,clip-systems.ly}
+For more information on output formats, see @rprogram{Invoking LilyPond}.

 
 
 @node Including LilyPond files
 
 
 @node Including LilyPond files


@@ -359,7 +357,7 @@ together the individual instrument files.
 
 The initialization of LilyPond is done in a number of files that are
 included by default when you start the program, normally transparent to the
 
 The initialization of LilyPond is done in a number of files that are
 included by default when you start the program, normally transparent to the

-user.  Run lilypond --verbose to see a list of paths and files that Lily
+user.  Run @code{lilypond --verbose} to see a list of paths and files that Lily

 finds.
 
 Files placed in directory @file{PATH/TO/share/lilypond/VERSION/ly/} (where
 finds.
 
 Files placed in directory @file{PATH/TO/share/lilypond/VERSION/ly/} (where


@@ -371,7 +369,7 @@ available to \include from directories in the search path specified as an
 option when invoking @code{lilypond --include=DIR} which adds DIR to the
 search path.
 
 option when invoking @code{lilypond --include=DIR} which adds DIR to the
 search path.
 

-The @code{\include} statement can use full path information, but with the Unix
+The @code{\include} statement can use full path information, but with the UNIX

 convention @code{/} rather than the DOS/Windows @code{\}.  For example,
 if @file{stuff.ly} is located one directory higher than the current working
 directory, use
 convention @code{/} rather than the DOS/Windows @code{\}.  For example,
 if @file{stuff.ly} is located one directory higher than the current working
 directory, use


@@ -433,11 +431,6 @@ To use a Unicode escape sequence, use
 @end example
 
 
 @end example
 
 

-@seealso
-
-@c @lsr{text,utf-8.ly}
-
-

 @node Different editions from one source
 @subsection Different editions from one source
 
 @node Different editions from one source
 @subsection Different editions from one source
 


@@ -490,7 +483,8 @@ commands, tagged expressions can be filtered.  For example,
 @end example
 would yield
 
 @end example
 would yield
 

-@lilypondfile[ragged-right,quote]{tag-filter.ly}
+@c FIXME: broken
+@c @lilypondfile[ragged-right,quote]{tag-filter.ly}

 
 The arguments of the @code{\tag} command should be a symbol
 (such as @code{#'score} or @code{#'part}), followed by a
 
 The arguments of the @code{\tag} command should be a symbol
 (such as @code{#'score} or @code{#'part}), followed by a


@@ -502,11 +496,6 @@ a piece of music with multiple @code{\tag} entries,
 @end example
 
 
 @end example
 
 

-@seealso
-
-Examples: @c @lsr{parts,tag@/-filter@/.ly}
-
-

 @knownissues
 
 Multiple rests are not merged if you create the score with both tagged
 @knownissues
 
 Multiple rests are not merged if you create the score with both tagged


@@ -527,7 +516,7 @@ sections.
 
 TODO: everything
 
 
 TODO: everything
 

-By default, lilypnod does a pretty jazz'n job of picking
+By default, LilyPond does a pretty jazz'n job of picking

 directions.  But in some cases, it may be desirable to force a
 direction.
 
 directions.  But in some cases, it may be desirable to force a
 direction.
 


@@ -672,7 +661,7 @@ I do think that a list like this, with the main contexts and a
 brief
 description of  what they do (perhaps also with a note about what
 default
 brief
 description of  what they do (perhaps also with a note about what
 default

-behaviour is associated with each of them, but this may be
+behavior is associated with each of them, but this may be

 unmanageable),
 should be there, and then we could simply list the remaining ones
 without
 unmanageable),
 should be there, and then we could simply list the remaining ones
 without


@@ -852,5 +841,3 @@ http://lists.gnu.org/archive/html/lilypond-user/2006-11/msg00061.html
 \fretmode ?
 
 
 \fretmode ?
 
 

-
-