From 9f38e95c4feba22a65e66a1d58b9f34d23c0e26e Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Thu, 28 Feb 2008 23:37:54 -0800 Subject: [PATCH] Small reminders and formatting tweaks. --- Documentation/user/fundamental.itely | 6 +++--- Documentation/user/input.itely | 5 +++++ Documentation/user/macros.itexi | 3 ++- Documentation/user/tutorial.itely | 4 ++-- Documentation/user/working.itely | 2 +- 5 files changed, 13 insertions(+), 7 deletions(-) diff --git a/Documentation/user/fundamental.itely b/Documentation/user/fundamental.itely index 1e56b0e4f2..89a0d051cd 100644 --- a/Documentation/user/fundamental.itely +++ b/Documentation/user/fundamental.itely @@ -40,7 +40,7 @@ description of the input format, see @ruser{File structure}. A basic example of a lilypond input file is @example -\version "2.11.38" +\version "@version{}" \score @{ @var{...compound music expression...} % all the music goes here! \header @{ @} @@ -1589,7 +1589,7 @@ engraver is removed from a context it can no longer produce its output. This is a crude way of modifying the output, but it can sometimes be useful. -@subsubsection Changing a single context +@subsubheading Changing a single context To remove an engraver from a single context we use the @code{\with} command placed immediately after the context creation @@ -1670,7 +1670,7 @@ the notes in all the voices on that staff: >> @end lilypond -@subsubsection Changing all contexts of the same type +@subsubheading Changing all contexts of the same type The examples above show how to remove or add engravers to individual contexts. It is also possible to remove or add diff --git a/Documentation/user/input.itely b/Documentation/user/input.itely index 0a02af5d37..9ad929c4af 100644 --- a/Documentation/user/input.itely +++ b/Documentation/user/input.itely @@ -548,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 diff --git a/Documentation/user/macros.itexi b/Documentation/user/macros.itexi index b0dafefd95..cf268fafb3 100644 --- a/Documentation/user/macros.itexi +++ b/Documentation/user/macros.itexi @@ -6,8 +6,9 @@ version that you are working on. See TRANSLATION for details. @end ignore -@macro version +@c FIXME: will deal with later. @c @value{version} +@macro version 2.11.41 @end macro diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index c4681c27cc..e860017451 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -1585,7 +1585,7 @@ The @code{\version} statement records the version of LilyPond that was used to write the file: @example -\version "2.11.38" +\version "@version{}" @end example @noindent @@ -1607,7 +1607,7 @@ main music expression; the @code{\header} block is usually placed underneath the @ref{Version number}. @example -\version "2.11.38" +\version "@version{}" \header @{ title = "Symphony" composer = "Me" diff --git a/Documentation/user/working.itely b/Documentation/user/working.itely index 36e8e0140c..59e2ff3fc3 100644 --- a/Documentation/user/working.itely +++ b/Documentation/user/working.itely @@ -536,7 +536,7 @@ file with @code{\include "../global.ly"}, which contains @example %%% global.ly -\version "2.11.38" +\version "@version{}" #(ly:set-option 'point-and-click #f) \include "../init/init-defs.ly" \include "../init/init-layout.ly" -- 2.39.5