Docs: change 'local-doc' make target meaning

[lilypond.git] / Documentation / notation / spacing.itely

diff --git a/Documentation/notation/spacing.itely b/Documentation/notation/spacing.itely
index bd844e3ebe5fb7aa81b138ef3e86e5677f7c21b0..70ef916fc02942708956dfb0b5ce4ef2fe20d34f 100644 (file)
--- a/Documentation/notation/spacing.itely
+++ b/Documentation/notation/spacing.itely
@@ -248,8 +248,12 @@ footer.  Default: @code{4\mm}.
 @item head-separation
 @funindex head-separation
 
-Distance between the top-most music system and the page header.
-Default: @code{4\mm}.
+Distance between the header markup (@code{oddHeaderMarkup} and
+@code{evenHeaderMarkup}) and the title markup
+(@code{bookTitleMarkup}, @code{title}, and others).  If the header
+markup and title markup are not present, it is the distance
+between @code{top-margin} and the spot where the title markup
+would normally appear.  Default: @code{4\mm}.
 
 @item page-top-space
 @funindex page-top-space
@@ -936,11 +940,6 @@ but the value can be changed in the @code{\paper} block:
 @}
 @end example
 
-@c TODO Check this -td
-The old page breaking algorithm is called
-@code{optimal-page-breaks}.  If you are having trouble with the new page
-breakers, you can enable the old one as a workaround.
-
 @funindex \bookpart
 
 When a book has many scores and pages, the page breaking problem may be
@@ -1303,6 +1302,9 @@ first number is generally negative.  The numbers need not match;
 for example, the staff can be made larger at the bottom by setting
 it to @code{(-6 . 4)}.
 
+@ignore
+FIXME: update this section
+
 After page breaks are determined, the vertical spacing within each
 system is reevaluated in order to fill the page more evenly; if a page
 has space left over, systems are stretched in order to fill that space.
@@ -1364,6 +1366,7 @@ the second piano staff:
 }
 }
 @end lilypond
+@end ignore
 
 Vertical alignment of staves is handled by the
 @code{VerticalAlignment} object.  The context parameters
@@ -1901,7 +1904,10 @@ c2 c4. c8 c4. c16[ c] c4. c8 c8 c8 c4 c4 c4
 @end lilypond
 
 
-In the introduction (see @rlearning{Engraving}), it was explained that stem
+In the introduction
+FIXME FIXME FIXME
+@c (see @rlearning{Engraving}), 
+it was explained that stem
 directions influence spacing.  This is controlled with the
 @code{stem-spacing-correction} property in the
 @rinternals{NoteSpacing}, object.  These are generated for every