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

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

diff --git a/Documentation/user/input.itely b/Documentation/user/input.itely
index dcfd9176c0d79d5ea8860842c07c378e3b931772..5cb75d34927913391f06809096767b97dae7babe 100644 (file)
--- a/Documentation/user/input.itely
+++ b/Documentation/user/input.itely
@@ -16,6 +16,12 @@ 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
 
 
@@ -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
-* Up and down::                 
+* Controlling direction and placement::  
 * Distances and measurements MAYBE MOVE::  
+* When to add a -::             
 @end menu
 
-@node Up and down
-@subsection Up and down
+@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.
 
@@ -537,6 +544,15 @@ Also cover
 
 Maybe rename section to "directions".
 
+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
@@ -546,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?
@@ -647,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
@@ -827,5 +852,3 @@ http://lists.gnu.org/archive/html/lilypond-user/2006-11/msg00061.html
 \fretmode ?
 
 
-
-