From 2fa98535accc93387d5213374c9aa822cf8b7005 Mon Sep 17 00:00:00 2001 From: Han-Wen Nienhuys Date: Sun, 25 May 2003 20:57:54 +0000 Subject: [PATCH] *** empty log message *** --- ChangeLog | 1 + Documentation/user/refman.itely | 49 ++------- Documentation/user/tutorial.itely | 160 ++++++++++++------------------ 3 files changed, 73 insertions(+), 137 deletions(-) diff --git a/ChangeLog b/ChangeLog index ae223fe91b..3810b63aab 100644 --- a/ChangeLog +++ b/ChangeLog @@ -70,6 +70,7 @@ * lilypond-indent.el: Add a message about trying to match \] or \). 2003-05-22 Juergen Reuter + * input/test/gregorian-scripts.ly, input/test/vaticana.ly: removed obsolete "arithmetic_*" diff --git a/Documentation/user/refman.itely b/Documentation/user/refman.itely index b555134120..64f600bc6a 100644 --- a/Documentation/user/refman.itely +++ b/Documentation/user/refman.itely @@ -2377,7 +2377,7 @@ length is omitted, then then the last value (stored in c'2:8 c':32 | c': c': | @end lilypond -[TODO : stok is te kort bij 32en] +@c [TODO : stok is te kort bij 32en] @refbugs @@ -4091,29 +4091,6 @@ arbitrary line, as described in section @ref{Clef}. The note printed to the right side of each clef in the example column denotes the @code{c'} with respect to that clef. -@c --- This should go somewhere else: --- -@c @item modern style G clef (glyph: @code{clefs-G}) -@c -@c Supported clefs: -@c @code{treble}, @code{violin}, @code{G}, @code{G2}, @code{french} -@c -@c @lilypond[26pt]{\property Staff.TimeSignature \set #'transparent = ##t \clef "G" c'} -@c -@c @item modern style F clef (glyph: @code{clefs-F}) -@c -@c Supported clefs: -@c @code{varbaritone}, @code{bass}, @code{F}, @code{subbass} -@c -@c @lilypond{\property Staff.TimeSignature \set #'transparent = ##t \clef "F" c'} -@c -@c @item modern style C clef (glyph: @code{clefs-C}) -@c -@c Supported clefs: -@c @code{soprano}, @code{mezzosoprano}, @code{alto}, @code{C}, -@c @code{tenor}, @code{baritone} -@c -@c @lilypond{\property Staff.TimeSignature \set #'transparent = ##t \clef "C" c'} - @multitable @columnfractions .3 .3 .3 .1 @item @@ -6329,7 +6306,7 @@ vocabulary. With this expansion, many innovations in musical notation have been tried. For a comprehensive overview, refer to @cite{Stone 1980} (see @ref{Literature}). In general, the use of new, innovative notation makes a piece harder to understand and perform and its use -should be avoided if possible. For this reason, support for +should therefore be avoided if possible. For this reason, support for contemporary notation in LilyPond is limited. @@ -7332,25 +7309,21 @@ choose sensible page breaks in multi-page pieces. Entered music can also be converted to MIDI output. The performance is good enough for proof-hearing the music for errors. - Ties, dynamics and tempo changes are interpreted. Dynamic marks, crescendi and decrescendi translate into MIDI volume levels. Dynamic marks translate to a fixed fraction of the available MIDI volume -range, crescendi and decrescendi make the volume vary linearly -between their two extremities. The fractions be adjusted by +range, crescendi and decrescendi make the volume vary linearly between +their two extremities. The fractions be adjusted by @code{dynamicAbsoluteVolumeFunction} in @internalsref{Voice} context. - -For each type of musical instrument (that MIDI supports), a volume range -can be defined. This gives you basic equalizer control, which can -enhance the quality of the MIDI output remarkably. The equalizer -can be controlled by setting @code{instrumentEqualizer}. - -Both loudness controls are combined to produce the final MIDI volume. +For each type of MIDI instrument, a volume range can be defined. This +gives you basic equalizer control, which can enhance the quality of +the MIDI output remarkably. The equalizer can be controlled by +setting @code{instrumentEqualizer}. @refbugs Many musically interesting effects, such as swing, articulation, -slurring, etc., are translated to MIDI. +slurring, etc., are not translated to MIDI. @menu @@ -7369,8 +7342,8 @@ simpler. The @code{\midi} block can contain: @cindex MIDI block @itemize @bullet - @item a @code{\tempo} definition - @item context definitions + @item a @code{\tempo} definition + @item context definitions @end itemize Assignments in the @code{\midi} block are not allowed. diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index 86f4567c29..9bd2772e67 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -20,9 +20,9 @@ * Printing lyrics:: * A lead sheet:: * Listening to output:: -* More movements :: Joining separate pieces of music +* Titling :: * Single staff polyphony :: -* Piano music:: +* Piano staffs:: * Organising larger pieces:: * Fine tuning a piece:: * An orchestral score:: Conductor's score and individual parts @@ -911,8 +911,20 @@ reference manual section @ref{Chords}. @cindex lead sheet When put together, chord names, lyrics and a melody form -a lead sheet, for example: -@lilypond[singleline,verbatim] +a lead sheet, for example, + +@example +\score @{ + < + \context ChordNames \chords @{ @emph{chords} @} + \addlyrics + \notes @emph{the melody} + \context Lyrics \lyrics @{ @emph{the text} @} + > + \paper @{ @} +@} +@end example +@lilypond[singleline] \score { < \context ChordNames \chords { r8 c2:sus4 f } @@ -950,117 +962,67 @@ example @end example Here, the tempo is specified using the @code{\tempo} command. In this -case the tempo of quarter notes is set to 72 beats per minute. - - -@node More movements -@section More movements - -The program @code{lilypond} only produces sheet music. Titles, -subtitles, and the composer's name are created by a separate program, -called use @code{ly2dvi}. @code{ly2dvi} creates the titles, then -calls @code{lilypond} to format the sheet music. In this section, we -show you how to create titles like this: - -@center @strong{Two miniatures} -@flushright -F. Bar Baz - -Opus 1. -@end flushright -@flushleft -@var{Up} -@end flushleft -@lilypond - \score { - \notes { c'4 d'4 } - \paper { raggedright = ##t } - } -@end lilypond -@flushright -Opus 2. -@end flushright -@flushleft -@var{Down} -@end flushleft -@lilypond - \score { - \notes { d'4 c'4 } - \paper { linewidth = -1.0 } - } -@end lilypond +case the tempo of quarter notes is set to 72 beats per minute. More +information on auditory output is in the @ref{Sound} section in the +notation manual. -For example, consider the following file (@file{miniatures.ly}) -@example -\header @{ - title = "Two miniatures" - composer = "F. Bar Baz" - tagline = "small is beautiful" @} +@node Titling +@section Titling -\score @{ - \notes @{ c'4 d'4 @} - \header @{ - opus = "Opus 1." - piece = "Up" @} -@} -\score @{ - \notes @{ d'4 c'4 @} - \header @{ - opus = "Opus 2." - piece = "Down" @} -@} -@end example - - -The information for the global titling is in a so-called header block. -The information in this block is not used by LilyPond, but it is -passed into @code{ly2dvi}, which uses this information to print titles -above the music. -@cindex assignments -@cindex identifier assignment -the @code{\header} block contains assignments. In each assignment, a -variable is set to a value. The header block for this file looks like -this -@cindex @code{\header} +Bibliographic information is entered in a separate block, the +@code{\header} block. The name of the piece, its composer, etc. are +entered as assignment within @code{\header @{ @dots{} @}}. For +example, @example \header @{ - title = "Two miniatures" - composer = "F. Bar Baz" + title = "Eight miniatures" + composer = "Igor Stravinsky" tagline = "small is beautiful" @} + + \score { @dots{} @end example -When you process a file with ly2dvi, a signature line is printed at -the bottom of the last page. Many people find the default (``Lily was -here'' with a version number) too droll. If that is the case, you can -change @code{tagline} in the @code{\header}, as shown above. +@cindex bibliographic information +@cindex titles +@cindex composer +@cindex ly2dvi + + +When the file is processed by @code{ly2dvi}, the title and composer +specified are printed above the music. The `tagline' is a short line +printed at bottom of the last page, which normally says ``Lily was +here, version @dots{}''. In the example above, it is replaced by the +line ``small is beautiful.'' + +Normally, the @code{\header} is put at the top of the file. However, +for a document that contains multiple pieces (e.g. a etude book, or +part with multiple movements), then the header can be put into the +@code{\score} block as follows In this case, the name of each piece +will be printed before each movement. + @cindex Lily was here @cindex signature line @cindex tag line - -@separate -@example - \header @{ +@example + \header @{ + title = "Eight miniatures" + composer = "Igor Stravinsky" + tagline = "small is beautiful" + @} + + \score { @dots{} + \header @{ piece = "Adagio" @} + } + \score { @dots{} + \header @{ piece = "Menuetto" @} + } @end example -The @code{\header} is normally at the top of the file, where it sets -values for the rest of the file. If you want to typeset different -pieces from one file (for example, if there are multiple movements, or -if you are making an exercise book), you can put different -@code{\score} blocks into the input file. @code{ly2dvi} will assemble -all LilyPond output files into a one document. The contents of -@code{\header} blocks specified within each score is used for the -title of that movement. -@separate -@example - opus = "Opus 1." - piece = "Up" @} -@end example -For example, the Opus number is put at the right, and the "piece" string -will be at the left. +More information on titling can be found in @ref{Invoking ly2dvi}. @node Single staff polyphony -- 2.39.5