From 43b15b9a9a79a9b1b246e9829a27e56137c1d1a8 Mon Sep 17 00:00:00 2001 From: Graham Percival Date: Tue, 3 May 2005 11:29:34 +0000 Subject: [PATCH] New chapter, changes to table of contents. --- ChangeLog | 9 +++++ Documentation/user/examples.itely | 64 ++++--------------------------- Documentation/user/lilypond.tely | 8 ++-- 3 files changed, 22 insertions(+), 59 deletions(-) diff --git a/ChangeLog b/ChangeLog index cbd058f4aa..bd546918a0 100644 --- a/ChangeLog +++ b/ChangeLog @@ -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 * scm/framework-ps.scm (write-preamble): extract CFF from OTF diff --git a/Documentation/user/examples.itely b/Documentation/user/examples.itely index b1226f5299..0910c1f2ba 100644 --- a/Documentation/user/examples.itely +++ b/Documentation/user/examples.itely @@ -8,64 +8,16 @@ beautiful printed scores! @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 -@c TODO explain \score{} ? Maybe add a note to the tutorial? - -@node Suggestions for writing LilyPond files -@section 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: - -@itemize @bullet -@item 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. - -@item 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. - -@item 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. - -@item 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. - -@end itemize @node Single staff @section Single staff diff --git a/Documentation/user/lilypond.tely b/Documentation/user/lilypond.tely index 4dda8df08e..904a997844 100644 --- a/Documentation/user/lilypond.tely +++ b/Documentation/user/lilypond.tely @@ -253,6 +253,8 @@ of this and other documentation. * 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 @@ of this and other documentation. * 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 @@ of this and other documentation. @include introduction.itely @include tutorial.itely @include examples.itely +@include putting.itely @include invoking.itely @include basic-notation.itely @include instrument-notation.itely -- 2.39.5