+2006-04-04 Graham Percival <gpermus@gmail.com>
+
+ * Documentation/user/ basic-notation, advanced-notation, putting,
+ instrument-notation, invoking, lilypond, THANKS: another ream of small
+ fixes from the Doc Helpers.
+
2006-04-03 David Feuer <David.Feuer@gmail.com>
* music-drawing-routines.ps: remove superfluous gsave/grestore pairs.
@code{textSpannerNeutral}.
+@commonprop
+
+To print a solid line, use
+
+@example
+\override TextSpanner #'dash-fraction = #'()
+@end example
+
+
@seealso
Program reference: @internalsref{TextSpanner}.
@itemize @bullet
@item @code{font-encoding}
is a symbol that sets layout of the glyphs. This should only be set to
-select different types of non-text fonts, eg.
+select different types of non-text fonts, e.g.
@code{fetaBraces} for piano staff braces, @code{fetaMusic} the
standard music font, including ancient glyphs, @code{fetaDynamic} for
@c Yes, this is good practice. Otherwise, the start of the original
@c part can only be seen from the font size. This is not good enough
@c for sight-reading. It is possilbe to use other
-@c markers (eg. a big close-bracket over the staff) to indicate the cue notes are
+@c markers (e.g. a big close-bracket over the staff) to indicate the cue notes are
@c finished.
@c -hwn
Shape note heads are implemented through the @code{shapeNoteStyles}
property. Its value is a vector of symbols. The k-th element indicates
the style to use for the k-th step of the scale. Arbitrary
-combinations are possible, eg.,
-
+combinations are possible, e.g.
@lilypond[verbatim,relative=1,fragment]
\set shapeNoteStyles = ##(cross triangle fa #f mensural xcircle diamond)
@commonprop
-In accordance with standard typsetting rules, a natural sign is printed
+In accordance with standard typesetting rules, a natural sign is printed
before a sharp or flat if a previous accidental needs to be
cancelled. To change this behaviour, use
@code{\set Staff.extraNatural = ##f}
single bar as well as many bars, and are discussed in
@ref{Multi measure rests}.
-
-A rest's vertical position may be explicitly specified by entering a
-note with the @code{\rest} keyword appended, the rest will be placed at
-the note's place. This makes manual formatting in polyphonic music
-easier. Automatic rest collision formatting will leave these rests
-alone
+To explicitly specify a rest's vertical position, write a note
+followed by @code{\rest}. A rest will be placed in the position
+where the note would appear,
@lilypond[fragment,quote,ragged-right,verbatim]
a'4\rest d'4\rest
@end lilypond
+@noindent
+This makes manual formatting of
+polyphonic music much easier, since the automatic rest collision
+formatter will leave these rests alone.
+
@seealso
Program reference: @internalsref{Rest}.
@cindex @code{.}
-To obtain dotted note lenghts, simply add a dot (`@code{.}') to
+To obtain dotted note lengths, simply add a dot (`@code{.}') to
the number. Double-dotted notes are produced in a similar way.
@lilypond[quote,ragged-right,fragment,verbatim]
\transpose c bes @{ e4 @dots{} @}
@end example
-To print this music in B-flat again (ie producing a trumpet part,
+To print this music in B-flat again (i.e. producing a trumpet part,
instead of a concert pitch conductor's score) you would wrap the
existing music with another @code{transpose}
of magnitude quicker than rendering it completely
Skipping parts of a score can be controlled in a more fine-grained
-fashing with the property @code{Score.skipTypesetting}. When it is
+fashion with the property @code{Score.skipTypesetting}. When it is
set, no typesetting is performed at all.
This property is also used to control output to the MIDI file. Note that
@cindex varbaritone clef
@cindex subbass clef
-Supported clefs finclude
+Supported clefs include
@table @code
@item treble, violin, G, G2
G clef on 2nd line
@noindent
Ties are used either when the note crosses a bar line, or when dots
cannot be used to denote the rhythm. When using ties, larger note
-values should be aligned to subdivisions of the measure, eg.
+values should be aligned to subdivisions of the measure, such as
@lilypond[fragment,quote,ragged-right]
\relative {
When a second alternative of a repeat starts with a tied note, you
have to repeat the tie. This can be achieved with @code{\repeatTie},
-eg.
@lilypond[fragment,quote,ragged-right,relative=2]
r <c e g>\repeatTie
@node Polyphony
@section Polyphony
-Polyphony in music refers to having more than one voice occuring in
+Polyphony in music refers to having more than one voice occurring in
a piece of music. Polyphony in LilyPond refers to having more than
one voice on the same staff.
voice. Note that the change to the note-head style in the main voice does not affect
the inside of the @code{<< \\ >>} constructs. Also, the change to the second
voice in the first @code{<< \\ >>} construct is effective in the second
-@code{<< \\ >>}, and the voice is tied accross the two constructs.
+@code{<< \\ >>}, and the voice is tied across the two constructs.
@lilypond[quote,verbatim,fragment]
\new Staff \relative c' {
}
@end lilypond
-Avoiding the @code{\\} seperator also allows nesting polyphony
+Avoiding the @code{\\} separator also allows nesting polyphony
constructs, which in some case might be a more natural way to typeset
the music.
The @code{FiguredBass} context doesn't pay attention to the actual
bass line. As a consequence, you may have to insert extra figures to
get extender lines below all notes, and you may have to add @code{\!}
-to avoid getting an extender line, eg.
+to avoid getting an extender line, e.g.
@lilypond[relative=1]
<<
@item -d,--define-default=@var{var}=@var{val}
This sets the internal program option @var{var} to the Scheme value
@var{val}. If @var{val} is not supplied, then @var{#t} is used. To
-switch off an option, @code{no-} may be prefixed to @var{var}, eg.
+switch off an option, @code{no-} may be prefixed to @var{var}, e.g.
+
@example
-dno-point-and-click
@end example
@item Preparing the jail
LilyPond needs to read a number of files while running. All these files
-are to be copied into the jail, under the same path they apper in the
+are to be copied into the jail, under the same path they appear in the
real root filesystem. The entire content of the LilyPond installation
(e.g., @file{/usr/share/lilypond})
should be copied.
@end example
These locations are LilyPond's best guess about where the warning or
-error occured, but (by their very nature) warnings and errors occur
+error occurred, but (by their very nature) warnings and errors occur
when something unexpected happens. If you can't see an error in the
indicated line of your input file, try checking one or two lines
above the indicated position.
@direntry
@ignore
(I think)
-Current version of the manual: 2.7.39
+Current version of the manual: 2.8.0
****** Please update this whenever you run convert-ly on the docs.
convert-ly --from=... --to=... --no-version *.itely
or three years later, you won't know how your file is structured if you
didn't comment the file.
-@item Ident your braces. A lot of problems are caused by an imbalance
+@item Indent your braces. A lot of problems are caused by an imbalance
in the number of @code{@{} and @code{@}}.
@end itemize
-If you are entering music from an existing score (ie typesetting a
+If you are entering music from an existing score (i.e. typesetting a
piece of existing sheet music),
@itemize @bullet
@end lilypond
With @code{extra-offset}, the first number controls the horizontal
-movement (left is negative); the second number controls the vertial
+movement (left is negative); the second number controls the vertical
movement (up is positive). After a bit of experimenting, we decided
that these values look good
BUG HUNTERS/SUGGESTIONS
Aurèle Duda
+Christopher Ellis
David Rogers
J. Leung
Orm Finnendahl
projects / lilypond.git / commitdiff