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

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

diff --git a/Documentation/user/input.itely b/Documentation/user/input.itely
index 036367738b3f29df0ab23908576e8878afa73040..6ad8ecee80a2d5e89e725c1a72595476a5b8f990 100644 (file)
--- a/Documentation/user/input.itely
+++ b/Documentation/user/input.itely
@@ -10,12 +10,18 @@
 @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
 under heavy development.
 
+FIXME: add comments
+@verbatim
+% %{
+@end verbatim
+to 3.1.
+
 @menu
 * Input files::                 
 * Common syntax issues TODO name?::  
@@ -299,7 +305,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.
 
-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
 
 
@@ -325,7 +331,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.
 
-For more information on output formats, see @rprogram{Invoking lilypond}.
+For more information on output formats, see @rprogram{Invoking LilyPond}.
 
 @seealso
 
@@ -353,7 +359,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
-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
@@ -365,7 +371,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.
 
-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
@@ -501,7 +507,7 @@ a piece of music with multiple @code{\tag} entries,
 Examples: @c @lsr{parts,tag@/-filter@/.ly}
 
 
-@refbugs
+@knownissues
 
 Multiple rests are not merged if you create the score with both tagged
 sections.
@@ -511,16 +517,17 @@ sections.
 @section Common syntax issues TODO name?
 
 @menu
-* Controlling direction::       
+* Controlling direction and placement::  
 * Distances and measurements MAYBE MOVE::  
+* When to add a -::             
 @end menu
 
-@node Controlling direction
-@subsection Controlling direction
+@node Controlling direction and placement
+@subsection Controlling direction and placement
 
 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.
 
@@ -541,6 +548,11 @@ Also mention \override Foo #'direction = #'DOWN.
 
 also mention the typical \fooDown, \fooNeutral predefined commands.
 
+also mention that some directions are (without other tweaking)
+always up or always down (like dynamics or fermata), while other
+things can alternate between up or down based on the stem direction
+(like slurs or accents).
+
 
 @node Distances and measurements MAYBE MOVE
 @subsection Distances and measurements MAYBE MOVE
@@ -550,7 +562,16 @@ DISCUSS after working on other sections.
 TODO: staff spaces, #UP #DOWN #LEFT #RIGHT.  Maybe move into tweaks?
 
 
+@node When to add a -
+@subsection When to add a -
 
+One of these works, the other doesn't.
+
+@verbatim
+\version "2.11.38"
+{ c'\mp\fermata\accent-\markup { "forcefully"} }
+% { c'\mp\fermata\accent\markup { "forcefully"} }
+@end verbatim
 
 
 @node Other stuffs TODO move?
@@ -651,7 +672,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
-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
@@ -831,5 +852,3 @@ http://lists.gnu.org/archive/html/lilypond-user/2006-11/msg00061.html
 \fretmode ?
 
 
-
-