From a0c4d20923751b9992c44158f88c960e97ce558f Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Fri, 6 May 2005 10:54:40 +0000 Subject: [PATCH] Really minor fixes. --- ChangeLog | 5 +++++ Documentation/user/advanced-notation.itely | 1 - Documentation/user/global.itely | 2 ++ Documentation/user/introduction.itely | 2 +- Documentation/user/putting.itely | 2 +- Documentation/user/tutorial.itely | 6 +++--- 6 files changed, 12 insertions(+), 6 deletions(-) diff --git a/ChangeLog b/ChangeLog index 94867e08b0..55dc752c4c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2005-05-06 Graham Percival + + * Documentation/user/advanced-notation.itely, putting.itely, + tutorial.itely, global.itely, introduction.itely: really minor fixes. + 2005-05-06 Jan Nieuwenhuizen * mf/GNUmakefile (MFTRACE_FLAGS): diff --git a/Documentation/user/advanced-notation.itely b/Documentation/user/advanced-notation.itely index cd23b7a53a..5cfc3c86e9 100644 --- a/Documentation/user/advanced-notation.itely +++ b/Documentation/user/advanced-notation.itely @@ -295,7 +295,6 @@ It is also possible to print dynamics in round parenthesis or square brackets. These are often used for adding editorial dynamics. @lilypond[quote,verbatim,raggedright] -\version "2.4.2" rndf = \markup{ \center-align {\line { \bold{\italic (} \dynamic f \bold{\italic )} }} } boxf = \markup{ \bracket { \dynamic f } } diff --git a/Documentation/user/global.itely b/Documentation/user/global.itely index 3cfaf88661..df904fb230 100644 --- a/Documentation/user/global.itely +++ b/Documentation/user/global.itely @@ -688,6 +688,8 @@ and texts are entered with a @code{\markup} block, @} @end example +@cindex @code{\book} + The movements and texts are combined together in a @code{\book} block, like diff --git a/Documentation/user/introduction.itely b/Documentation/user/introduction.itely index 7aecfb286c..7d70a7108b 100644 --- a/Documentation/user/introduction.itely +++ b/Documentation/user/introduction.itely @@ -843,7 +843,7 @@ vary from system to system. On occasion, this manual refers to initialization and example files. Throughout this manual, we refer to input files relative to the top-directory of the source archive. For example, @file{input/@/test/@/bla@/.ly} may refer to the file -@file{lilypond@/-2.4.0/@/input/@/test/@/bla@/.ly}. On binary packages +@file{lilypond@/-2.6.0/@/input/@/test/@/bla@/.ly}. On binary packages for the Unix platform, the documentation and examples can typically be found somewhere below @file{/usr/@/share/@/doc/@/lilypond/}. Initialization files, for example @file{scm/@/lily@/.scm}, or diff --git a/Documentation/user/putting.itely b/Documentation/user/putting.itely index 28f3e4a8ae..b5c6e1a249 100644 --- a/Documentation/user/putting.itely +++ b/Documentation/user/putting.itely @@ -31,7 +31,7 @@ problems: @itemize @bullet @item Include @code{\version} numbers in every file. Note that all -templates contain a @code{\version "2.4.0"} string. We +templates contain a @code{\version "2.6.0"} string. We highly recommend that you always include the @code{\version}, no matter how small your file is. Speaking from personal experience, it's quite frustrating to try to remember which version of LilyPond you were diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index 0efc80eedf..714c2f445c 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -904,7 +904,7 @@ ignored. The following fragment shows possible uses for comments %@} @end example -@c TODO post-2.4 reorg +@c TODO post-2.6 reorg @c This is good info, but I wouldn't call it a comment. IMO it should @c be moved somewhere else. @@ -912,10 +912,10 @@ ignored. The following fragment shows possible uses for comments There is a special statement that is a kind of comment. The @code{\version} statement marks for which version of LilyPond the file was written. -To mark a file for version 2.4.0, use +To mark a file for version 2.6.0, use @example -\version "2.4.0" +\version "2.6.0" @end example @noindent -- 2.39.5