Minor stuff from mailist.

diff --git a/ChangeLog b/ChangeLog
index b29dc5e7127bf3fd87c5791247dfe24124462989..9a0270d1bb4b0bfefe0b0660d353bf8f159d9581 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2006-02-23  Graham Percival  <gpermus@gmail.com>
+
+       * Documentation/user/ basic-notation, advanced-notation,
+       global.itely: minor fixes from mailist.
+
 2006-02-23  Heikki Junes  <hjunes@cc.hut.fi>
 
        * Documentation/index.html.in: changes concern the previous release.

diff --git a/Documentation/user/advanced-notation.itely b/Documentation/user/advanced-notation.itely
index 6daa4ea420e8f300d5cd8eef18094a7932c67e34..ee50987f10026637ff0cd287e1a6a85272b55445 100644 (file)
--- a/Documentation/user/advanced-notation.itely
+++ b/Documentation/user/advanced-notation.itely
@@ -1704,7 +1704,7 @@ c4 c1
 
 @noindent
 As the example illustrates, @code{ly:make-moment n m} constructs a
-duration of n/m, for example @code{ly:make-moment 1 8} is an eighth
+duration of n/m of a whole note.  For example, @code{ly:make-moment 1 8} is an eighth
 note duration and @code{ly:make-moment 7 16} is the duration of
 seven sixteenths notes.
 

diff --git a/Documentation/user/basic-notation.itely b/Documentation/user/basic-notation.itely
index d58ba1157d326cf51871faf52ac9d6a9f092e4c9..7d644e1e0065b6fdbe77c7fb8493b62ce87610a8 100644 (file)
--- a/Documentation/user/basic-notation.itely
+++ b/Documentation/user/basic-notation.itely
@@ -650,7 +650,7 @@ the @code{d} will generate a warning, because a @code{d''} is expected
 found.  In the output, the octave is corrected to be a @code{d''} and
 the next note is calculated relative to @code{d''} instead of @code{d'}.
 
-There is also a syntax that is separate from the notes.  The syntax
+There is also an octave check that produces no visible output.  The syntax
 
 @example
 \octave @var{pitch}
@@ -658,7 +658,7 @@ There is also a syntax that is separate from the notes.  The syntax
 
 This checks that @var{pitch} (without quotes) yields @var{pitch} (with
 quotes) in \relative mode.  If not, a warning is printed, and the
-octave is corrected.
+octave is corrected.  The @var{pitch} is not printed as a note.
 
 In the example below, the first check passes without incident, since
 the @code{e} (in relative mode) is within a fifth of @code{a'}.  However,

diff --git a/Documentation/user/global.itely b/Documentation/user/global.itely
index d3b932e08beca7b6093ad43a4f5c5d4497855fb4..2b96727b1efeff74e2b3ac99cafbefded25c2a95 100644 (file)
--- a/Documentation/user/global.itely
+++ b/Documentation/user/global.itely
@@ -241,8 +241,8 @@ directory, use
 LilyPond uses the Pango library to format multi-lingual texts, and
 does not perform any input-encoding conversions.  This means that any
 text, be it title, lyric text, or musical instruction containing
-non-ASCII characters, must be utf-8.  Easiest to enter such texts is
-by using a Unicode-aware editor, and save using utf-8 encoding.  Most
+non-ASCII characters, must be utf-8.  The easiest way to enter such text is
+by using a Unicode-aware editor and saving the file with utf-8 encoding.  Most
 popular modern editors have utf-8 support, for example, vim, Emacs,
 jEdit, and GEdit do.
 
@@ -632,8 +632,8 @@ Margin between the left side of the page and the beginning of the music.
 @item line-width
 The length of the systems.
 
-@cindex @code{heap-separation}
-@item heap-separation
+@cindex @code{head-separation}
+@item head-separation
 Distance between the top-most music system and the page header.
 
 @cindex @code{foot-separation}
@@ -1281,18 +1281,27 @@ exaggerated corrections:
 
 Proportional notation is supported; see @ref{Proportional notation}.
 
-@c  check this before release  --gp
-Symbol sizes (such as accidentals) may be disregarded for determining
-horizontal spacing,
+By default, spacing in tuplets depends on various non-duration
+factors (such as accidentals, clef changes, etc).  To disregard
+such symbols and force uniform equal-duration spacing, use
+@code{Score.SpacingSpanner #'uniform-stretching}.  This
+property can only be changed at the beginning of a score,
 
 @lilypond[quote,ragged-right,relative=2,fragment]
-<<
-  \time 2/4
-  \new Staff { c16[ c c c c c c c] c[ c c c c c c c] }
-  \new Staff {
-          c16[ cisis ces cis c cisis ces cis]
-    \override Score.SpacingSpanner #'uniform-stretching = ##t 
-          c16[ cisis ces cis c cisis ces cis]
+\new Score \with {
+  \override SpacingSpanner #'uniform-stretching = ##t
+} <<
+  \new Staff{
+    \times 4/5 {
+      c'8 c'8 c'8 c'8 c'8
+    }
+    c'8 c'8 c'8 c'8
+  }
+  \new Staff{
+    c'8 c'8 c'8 c'8
+    \times 4/5 {
+      c'8 c'8 c'8 c'8 c'8
+    }
   }
 >>
 @end lilypond
@@ -1630,6 +1639,27 @@ in the @code{\midi@{@}} section.
 @end example
 
 
+@refbugs
+
+Unterminated (de)crescendos will not render properly in the midi file,
+resulting in silent passages of music.  The workaround is to explicitly
+terminate the (de)crescendo.  For example,
+
+@example
+@{ a\< b c d\f @}
+@end example
+
+@noindent
+will not work properly but
+
+@example
+@{ a\< b c d\!\f @}
+@end example
+
+@noindent
+will.
+
+
 @node MIDI block
 @subsection MIDI block
 @cindex MIDI block