CVSROOT: /cvsroot/lilypond
Module name: lilypond
Branch:
Changes by: Graham Percival <[EMAIL PROTECTED]> 05/05/04 03:58:36
Modified files:
. : ChangeLog
Documentation/user: introduction.itely advanced-notation.itely
Log message:
Minor fixes.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/ChangeLog.diff?tr1=1.3545&tr2=1.3546&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/introduction.itely.diff?tr1=1.134&tr2=1.135&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/advanced-notation.itely.diff?tr1=1.17&tr2=1.18&r1=text&r2=text
Patches:
Index: lilypond/ChangeLog
diff -u lilypond/ChangeLog:1.3545 lilypond/ChangeLog:1.3546
--- lilypond/ChangeLog:1.3545 Tue May 3 22:33:59 2005
+++ lilypond/ChangeLog Wed May 4 03:58:35 2005
@@ -1,3 +1,9 @@
+2005-05-04 Graham Percival <[EMAIL PROTECTED]>
+
+ * Documentation/user/introduction.itely: updates "About this manual".
+
+ * Documentation/user/advanced-notation.itely: minor fixes.
+
2005-05-04 Han-Wen Nienhuys <[EMAIL PROTECTED]>
* COPYING: add font exception. Update FSF address.
Index: lilypond/Documentation/user/advanced-notation.itely
diff -u lilypond/Documentation/user/advanced-notation.itely:1.17
lilypond/Documentation/user/advanced-notation.itely:1.18
--- lilypond/Documentation/user/advanced-notation.itely:1.17 Tue May 3
12:13:28 2005
+++ lilypond/Documentation/user/advanced-notation.itely Wed May 4 03:58:36 2005
@@ -1900,52 +1900,6 @@
@end ignore
-
-
[EMAIL PROTECTED]
-
-FIXME: We don't need this section. It will be moved into LSR as soon
-as the safe mode stuff is worked out.
-
[EMAIL PROTECTED] ode Controlling formatting of prefatory matter
[EMAIL PROTECTED] ubsection Controlling formatting of prefatory matter
-
[EMAIL PROTECTED] This section will be moved to somewhere else soon. -gp
-This example demonstrates how to place prefatory matter
-(such as the clef and key signature) at the end of a line.
-
[EMAIL PROTECTED],verbatim]
-\transpose c c' {
- \override Staff.Clef
- #'break-visibility = #end-of-line-visible
- \override Staff.KeySignature
- #'break-visibility = #end-of-line-visible
- \set Staff.explicitClefVisibility = #end-of-line-visible
- \set Staff.explicitKeySignatureVisibility = #end-of-line-visible
-
- % We want the time sig to take space, otherwise there is not
- % enough white at the start of the line.
-
- \override Staff.TimeSignature #'transparent = ##t
- \set Score.defaultBarType = #"empty"
-
- c1 d e f g a b c
- \key d \major
- \break
-
- % see above.
- \time 4/4
-
- d e fis g a b cis d
- \key g \major
- \break
- \time 4/4
-}
[EMAIL PROTECTED] lilypond
-
[EMAIL PROTECTED] ignore
-
-
@node Coloring objects
@subsection Coloring objects
Index: lilypond/Documentation/user/introduction.itely
diff -u lilypond/Documentation/user/introduction.itely:1.134
lilypond/Documentation/user/introduction.itely:1.135
--- lilypond/Documentation/user/introduction.itely:1.134 Thu Apr 7
08:21:16 2005
+++ lilypond/Documentation/user/introduction.itely Wed May 4 03:58:36 2005
@@ -649,34 +649,75 @@
template into a file, add notes, and you're done!
@item
[EMAIL PROTECTED]@ref{Putting it all together}}
+demonstrates practical uses of LilyPond.
+
[EMAIL PROTECTED]
[EMAIL PROTECTED]
+The chapter
[EMAIL PROTECTED] ifhtml
[EMAIL PROTECTED]@ref{Running LilyPond}} shows how to run LilyPond and its
helper
+programs. In addition, this section explains how to upgrade input
+files from previous versions of LilyPond.
+
[EMAIL PROTECTED]
@ifhtml
The
@end ifhtml
[EMAIL PROTECTED] @[EMAIL PROTECTED] manual}} @c FIXME
[EMAIL PROTECTED] manual}
-discusses topics grouped by notation construct. Once you master the
-basics, this is the place to look up details.
[EMAIL PROTECTED]@ref{Basic notation}}
[EMAIL PROTECTED]
+chapter
[EMAIL PROTECTED] ifhtml
+discusses topics grouped by notation construct. This section gives
+details about basic notation that will be useful in almost any
+notation project.
@item
@ifhtml
The
@end ifhtml
[EMAIL PROTECTED]@ref{Changing defaults}}
-explains how to fine tune layout.
[EMAIL PROTECTED]@ref{Instrument-specific notation}}
[EMAIL PROTECTED]
+chapter
[EMAIL PROTECTED] ifhtml
+discusses topics grouped by notation construct. This section gives
+details about special notation that will only be useful for particular
+instrument (or vocal) groups.
@item
@ifhtml
-The chapter
+The
@end ifhtml
[EMAIL PROTECTED]@ref{Running LilyPond}} shows how to run LilyPond and its
helper
-programs.
[EMAIL PROTECTED]@ref{Advanced notation}}
[EMAIL PROTECTED]
+chapter
[EMAIL PROTECTED] ifhtml
+discusses topics grouped by notation construct. This section gives
+details about complicated or unusual notation.
+
[EMAIL PROTECTED]
[EMAIL PROTECTED]
+The
[EMAIL PROTECTED] ifhtml
[EMAIL PROTECTED]@ref{Global issues}}
[EMAIL PROTECTED]
+chapter
[EMAIL PROTECTED] ifhtml
+discusses issues which affect the whole lilypond file.
+
[EMAIL PROTECTED]
[EMAIL PROTECTED]
+The
[EMAIL PROTECTED] ifhtml
[EMAIL PROTECTED]@ref{Changing defaults}}
+explains how to fine tune layout.
@item
@ifhtml
The chapter
@end ifhtml
@[EMAIL PROTECTED] explains the details behind creating
-documents with in-line music examples (like this manual).
+documents with in-line music examples, like this manual.
@item
@ifhtml
@@ -685,8 +726,7 @@
@[EMAIL PROTECTED] from other formats}}
explains how to run the conversion programs. These programs
are supplied with the LilyPond package, and convert a variety of music
-formats to the @code{.ly} format. In addition, this section explains
-how to upgrade input files from previous versions of LilyPond.
+formats to the @code{.ly} format.
@item
@ifhtml
_______________________________________________
Lilypond-cvs mailing list
Lilypond-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-cvs
