CVSROOT: /cvsroot/lilypond
Module name: lilypond
Branch:
Changes by: Graham Percival <[EMAIL PROTECTED]> 05/05/03 11:29:34
Modified files:
. : ChangeLog
Documentation/user: lilypond.tely examples.itely
Log message:
New chapter, changes to table of contents.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/ChangeLog.diff?tr1=1.3532&tr2=1.3533&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/lilypond.tely.diff?tr1=1.124&tr2=1.125&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/examples.itely.diff?tr1=1.37&tr2=1.38&r1=text&r2=text
Patches:
Index: lilypond/ChangeLog
diff -u lilypond/ChangeLog:1.3532 lilypond/ChangeLog:1.3533
--- lilypond/ChangeLog:1.3532 Tue May 3 11:10:54 2005
+++ lilypond/ChangeLog Tue May 3 11:29:34 2005
@@ -15,6 +15,15 @@
* Documentation/user/global.itely: better docs for \header.
+ * Documentation/user/putting.itely: new chapter; placeholder
+ for future expansion.
+
+ * Documentation/user/examples.itely: moved "suggestions for
+ writing LP files" section into putting.itely.
+
+ * Documentation/user/lilypond.itely: added new chapter,
+ fixed the short table of contents.
+
2005-05-03 Han-Wen Nienhuys <[EMAIL PROTECTED]>
* scm/framework-ps.scm (write-preamble): extract CFF from OTF
Index: lilypond/Documentation/user/examples.itely
diff -u lilypond/Documentation/user/examples.itely:1.37
lilypond/Documentation/user/examples.itely:1.38
--- lilypond/Documentation/user/examples.itely:1.37 Sun Mar 20 02:58:39 2005
+++ lilypond/Documentation/user/examples.itely Tue May 3 11:29:34 2005
@@ -8,64 +8,16 @@
@c bad node name for ancient notation to avoid confict
@menu
-* Suggestions for writing LilyPond files::
-* Single staff::
-* Piano templates::
-* String quartet::
-* Vocal ensembles::
-* Ancient notation templates::
-* Jazz combo::
-* Other templates::
-* Lilypond-book templates::
+* Single staff::
+* Piano templates::
+* String quartet::
+* Vocal ensembles::
+* Ancient notation templates::
+* Jazz combo::
+* Other templates::
+* Lilypond-book templates::
@end menu
[EMAIL PROTECTED] TODO explain \score{} ? Maybe add a note to the tutorial?
-
[EMAIL PROTECTED] Suggestions for writing LilyPond files
[EMAIL PROTECTED] Suggestions for writing LilyPond files
-
-Now you're ready to begin writing larger LilyPond files -- not just the
-little examples in the tutorial, but whole pieces. But how should you
-go about doing it?
-
-The best answer is ``however you want to do it.'' As long as LilyPond
-can understand your files and produces the output that you want, it
-doesn't matter what your files look like. That said, sometimes we
-make mistakes when writing files. If LilyPond can't understand your
-files, or produces output that you don't like, how do you fix the
-problem?
-
-Here are a few suggestions that can help you to avoid or fix
-problems:
-
[EMAIL PROTECTED] @bullet
[EMAIL PROTECTED] Include @code{\version} numbers in every file. Note that all
-templates contain a @code{\version "2.4.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
-using a few years ago. @code{convert-ly} requires you to declare
-which version of LilyPond you used.
-
[EMAIL PROTECTED] Include checks: See @ref{Bar check} and @ref{Octave check}.
If you
-include checks every so often, then if you make a mistake, you can pinpoint
-it quicker. How often is ``every so often''? It depends on the complexity
-of the music. For very simple music, perhaps just once or twice. For
-very complex music, every bar.
-
[EMAIL PROTECTED] One bar per line. If there is anything complicated, either
in the music
-itself or in the output you desire, it's often good to write only one bar
-per line. Saving screen space by cramming eight bars per line just isn't
-worth it if you have to `debug' your files.
-
[EMAIL PROTECTED] Comment your files, with either bar numbers (every so often)
or
-references to musical themes (``second theme in violins'', ``fourth
-variation''). You may not need it when you're writing the piece for
-the first time, but if you want to go back and change something two
-or three years later, you won't know how your file is structured if you
-don't comment the file.
-
[EMAIL PROTECTED] itemize
@node Single staff
@section Single staff
Index: lilypond/Documentation/user/lilypond.tely
diff -u lilypond/Documentation/user/lilypond.tely:1.124
lilypond/Documentation/user/lilypond.tely:1.125
--- lilypond/Documentation/user/lilypond.tely:1.124 Thu Apr 21 15:20:45 2005
+++ lilypond/Documentation/user/lilypond.tely Tue May 3 11:29:34 2005
@@ -253,6 +253,8 @@
* Introduction:: What, Why, How.
* Tutorial:: A tutorial introduction.
* Example templates:: Larger examples.
+* Putting it all together:: Demonstrates real-life LilyPond usage.
+* Running LilyPond:: Operation.
* Basic notation:: Standard musical notation.
* Instrument-specific notation:: Notation that is only used for some
instruments.
@@ -261,15 +263,14 @@
* Changing defaults:: Tuning output.
* Interfaces for programmers::
-* Running LilyPond:: Operation.
-* Converting from other formats:: Converting to lilypond source format.
* LilyPond-book:: Integrating text and music.
+* Converting from other formats:: Converting to lilypond source format.
* Literature list::
* Scheme tutorial::
* Notation manual details::
* Point and click::
-* GNU Free Documentation License:: FDL.
* Cheat sheet::
+* GNU Free Documentation License:: FDL.
* Unified index::
@end menu
@end ifnottex
@@ -282,6 +283,7 @@
@include introduction.itely
@include tutorial.itely
@include examples.itely
[EMAIL PROTECTED] putting.itely
@include invoking.itely
@include basic-notation.itely
@include instrument-notation.itely
_______________________________________________
Lilypond-cvs mailing list
Lilypond-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-cvs
