CVSROOT: /cvsroot/lilypond
Module name: lilypond
Branch:
Changes by: Graham Percival <[EMAIL PROTECTED]> 05/05/06 10:54:40
Modified files:
. : ChangeLog
Documentation/user: advanced-notation.itely global.itely
introduction.itely putting.itely
tutorial.itely
Log message:
Really minor fixes.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/ChangeLog.diff?tr1=1.3558&tr2=1.3559&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/advanced-notation.itely.diff?tr1=1.18&tr2=1.19&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/global.itely.diff?tr1=1.10&tr2=1.11&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/introduction.itely.diff?tr1=1.136&tr2=1.137&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/putting.itely.diff?tr1=1.1&tr2=1.2&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/tutorial.itely.diff?tr1=1.253&tr2=1.254&r1=text&r2=text
Patches:
Index: lilypond/ChangeLog
diff -u lilypond/ChangeLog:1.3558 lilypond/ChangeLog:1.3559
--- lilypond/ChangeLog:1.3558 Fri May 6 10:41:16 2005
+++ lilypond/ChangeLog Fri May 6 10:54:40 2005
@@ -1,3 +1,8 @@
+2005-05-06 Graham Percival <[EMAIL PROTECTED]>
+
+ * Documentation/user/advanced-notation.itely, putting.itely,
+ tutorial.itely, global.itely, introduction.itely: really minor fixes.
+
2005-05-06 Jan Nieuwenhuizen <[EMAIL PROTECTED]>
* mf/GNUmakefile (MFTRACE_FLAGS):
Index: lilypond/Documentation/user/advanced-notation.itely
diff -u lilypond/Documentation/user/advanced-notation.itely:1.18
lilypond/Documentation/user/advanced-notation.itely:1.19
--- lilypond/Documentation/user/advanced-notation.itely:1.18 Wed May 4
03:58:36 2005
+++ lilypond/Documentation/user/advanced-notation.itely Fri May 6 10:54:40 2005
@@ -295,7 +295,6 @@
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 } }
Index: lilypond/Documentation/user/global.itely
diff -u lilypond/Documentation/user/global.itely:1.10
lilypond/Documentation/user/global.itely:1.11
--- lilypond/Documentation/user/global.itely:1.10 Tue May 3 12:53:43 2005
+++ lilypond/Documentation/user/global.itely Fri May 6 10:54:40 2005
@@ -688,6 +688,8 @@
@}
@end example
[EMAIL PROTECTED] @code{\book}
+
The movements and texts are combined together in a @code{\book} block,
like
Index: lilypond/Documentation/user/introduction.itely
diff -u lilypond/Documentation/user/introduction.itely:1.136
lilypond/Documentation/user/introduction.itely:1.137
--- lilypond/Documentation/user/introduction.itely:1.136 Thu May 5
22:13:58 2005
+++ lilypond/Documentation/user/introduction.itely Fri May 6 10:54:40 2005
@@ -843,7 +843,7 @@
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
[EMAIL PROTECTED]@/-2.4.0/@/input/@/test/@/bla@/.ly}. On binary packages
[EMAIL PROTECTED]@/-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
Index: lilypond/Documentation/user/putting.itely
diff -u lilypond/Documentation/user/putting.itely:1.1
lilypond/Documentation/user/putting.itely:1.2
--- lilypond/Documentation/user/putting.itely:1.1 Tue May 3 11:27:08 2005
+++ lilypond/Documentation/user/putting.itely Fri May 6 10:54:40 2005
@@ -31,7 +31,7 @@
@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
Index: lilypond/Documentation/user/tutorial.itely
diff -u lilypond/Documentation/user/tutorial.itely:1.253
lilypond/Documentation/user/tutorial.itely:1.254
--- lilypond/Documentation/user/tutorial.itely:1.253 Fri Apr 1 12:33:29 2005
+++ lilypond/Documentation/user/tutorial.itely Fri May 6 10:54:40 2005
@@ -904,7 +904,7 @@
[EMAIL PROTECTED]
@end example
[EMAIL PROTECTED] TODO post-2.4 reorg
[EMAIL PROTECTED] 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 @@
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
_______________________________________________
Lilypond-cvs mailing list
Lilypond-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-cvs
