From: Graham Percival <graham@percival-music.ca>
Date: Sun, 14 May 2006 01:53:54 +0000 (+0000)
Subject: Small fixes.
X-Git-Tag: release/2.9.5~21
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=3027a3f656baf9bcc8d9719da2a2feb9ba632599;p=lilypond.git

Small fixes.
---

diff --git a/ChangeLog b/ChangeLog
index 2448e18e93..4995fda109 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -5,6 +5,8 @@
 	* Documentation/user/programming-interface.itely: major
 	new docs, some reorg, some info from Nicolas.
 
+	* Documentation/user/ various: small fixes.
+
 2006-05-12  Mats Bengtsson  <mabe@drongo.s3.kth.se>
 
 	* Documentation/user/programming-interface.itely (Markup
diff --git a/Documentation/user/advanced-notation.itely b/Documentation/user/advanced-notation.itely
index b4335de9a0..bfadf74aa2 100644
--- a/Documentation/user/advanced-notation.itely
+++ b/Documentation/user/advanced-notation.itely
@@ -862,6 +862,12 @@ Bar numbers are printed by default at the start of the line.  The
 number itself is stored in the @code{currentBarNumber} property, which
 is normally updated automatically for every measure.
 
+To manually set a bar number, use
+
+@example
+\set Score.currentBarNumber = #57
+@end example
+
 Bar numbers can be typeset at regular intervals instead of at the
 beginning of each line.  This is illustrated in the following example,
 whose source is available as
diff --git a/Documentation/user/global.itely b/Documentation/user/global.itely
index f98e7c928a..e56de1e6fa 100644
--- a/Documentation/user/global.itely
+++ b/Documentation/user/global.itely
@@ -19,6 +19,7 @@ specific notation.
 * Music layout::                
 * Multiple movements::          
 * MIDI output::                 
+* Displaying LilyPond notation::  
 @end menu
 
 
@@ -1823,3 +1824,38 @@ If the selected instrument does not exactly match an instrument from
 the list of MIDI instruments, the Grand Piano (@code{"acoustic grand"})
 instrument is used.
 
+
+@c  Yes, this is a cop-out; this info doesn't belong in the Scheme
+@c  chapter, but I'm not certain where to stick it.
+@c  I think I'll eventually split this chapter into a "paper/layout"
+@c  chapter and a "misc issues" chapter.  -gp
+@node Displaying LilyPond notation
+@section Displaying LilyPond notation
+
+@cindex @code{\displayLilyMusc}
+Displaying a music expression in LilyPond notation can be
+done using the music function @code{\displayLilyMusic}.  For example,
+
+@example
+@{
+  \displayLilyMusic \transpose c a, @{ c e g a bes @}
+@}
+@end example
+
+will display
+
+@example
+@{ a, cis e fis g @}
+@end example
+
+By default, LilyPond will print these messages to the console along
+with all the other messages.  To split up these messages and save
+the results of @code{\display@{STUFF@}}, redirect the output to
+a file.
+
+@example
+lilypond file.ly >display.txt
+@end example
+
+
+
diff --git a/Documentation/user/tweaks.itely b/Documentation/user/tweaks.itely
index ae88bcb44a..11835602ff 100644
--- a/Documentation/user/tweaks.itely
+++ b/Documentation/user/tweaks.itely
@@ -7,6 +7,7 @@ configurable; virtually every fragment of output may be changed.
 
 
 @menu
+* Moving objects::              
 * Fixing overlapping notation::  
 * Common tweaks::               
 * Default files::               
@@ -14,8 +15,8 @@ configurable; virtually every fragment of output may be changed.
 @end menu
 
 
-@node Fixing overlapping notation
-@section Fixing overlapping notation
+@node Moving objects
+@section Moving objects
 
 This may come as a surprise, but LilyPond is not perfect.  Some notation
 elements can overlap.  This is unfortunate, but (in most cases) is easily
@@ -131,6 +132,48 @@ c4^"piu mosso" d e f
 This manual: @ref{The \override command}, @ref{Common tweaks}.
 
 
+@node Fixing overlapping notation
+@section Fixing overlapping notation
+
+In @ref{Moving objects}, we saw how to move a @code{TextScript}
+object.  The same mechanism can be used to move other types of
+objects; simply replace @code{TextScript} with the name of
+another object.
+
+To find the object name, look at the ``@strong{see also}'' at
+bottom of the relevant documentation page.  For example, at
+the bottom of @ref{Dynamics}, we see
+
+@quotation
+@seealso
+
+Program reference: @internalsref{DynamicText}, @internalsref{Hairpin}.
+Vertical positioning of these symbols is handled by
+@internalsref{DynamicLineSpanner}.
+@end quotation
+
+@noindent
+So to move dynamics around, we use
+
+@example
+\override DynamicLineSpanner #'padding = #2.0
+@end example
+
+We cannot list every object, but here is a list of the most
+common objects.
+
+@multitable @columnfractions .33 .66
+@headitem Object type  @tab Object name
+@item Text             @tab @code{TextScript}
+@item Dynamics         @tab @code{DynamicLineSpanner}
+@item Ties             @tab @code{Tie}
+@item Slurs            @tab @code{Slur}
+@item Articulation     @tab @code{Script}
+@item Fingering        @tab @code{Fingering}
+@item Rehearsal marks  @tab @code{RehearsalMark}
+@end multitable
+
+
 @node Common tweaks
 @section Common tweaks
 
diff --git a/Documentation/user/working.itely b/Documentation/user/working.itely
index c3d6950a86..57d081df6f 100644
--- a/Documentation/user/working.itely
+++ b/Documentation/user/working.itely
@@ -312,7 +312,7 @@ tempoMark = #(define-music-function (parser location markp) (string?)
 @end lilypond
 
 There are some problems with overlapping output; we'll fix those using
-the techniques in @ref{Fixing overlapping notation}.  But let's also
+the techniques in @ref{Moving objects}.  But let's also
 do something about the @code{mpdolce} and @code{tempoMark}
 definitions.  They produce the output we desire, but we might want
 to use them in another piece.  We could simply copy-and-paste them