Voice contexts can also be created manually
inside a @code{<< >>} block to create polyphonic music, using
-@code{\voiceOne} ... @code{\voiceFour} to indicate the required
+@code{\voiceOne} @dots{} @code{\voiceFour} to indicate the required
directions of stems, slurs, etc. In longer scores this method
is clearer, as it permits the voices to be separated and to be
given more descriptive names.
@noindent
Here, voices are instantiated explicitly and are given names. The
-@code{\voiceOne} ... @code{\voiceFour} commands set up the voices
+@code{\voiceOne} @dots{} @code{\voiceFour} commands set up the voices
so that first and third voices get stems up, second and fourth
voices get stems down, third and fourth voice note heads are
horizontally shifted, and rests in the respective voices are
This syntax can be used where it does not matter that temporary
voices are created and then discarded. These implicitly created
voices are given the settings equivalent to the effect of the
-@code{\voiceOne} ... @code{\voiceFour} commands, in the order in
+@code{\voiceOne} @dots{} @code{\voiceFour} commands, in the order in
which they appear in the code.
In the following example, the intermediate voice has stems up,
@section Fitting music onto fewer pages
Sometimes you can end up with one or two staves on a second
-(or third, or fourth...) page. This is annoying, especially
+(or third, or fourth@dots{}) page. This is annoying, especially
if you look at previous pages and it looks like there is plenty
of room left on those.
@notation{artık ikili} (12/9 or 13/9 of a tone).
From a modern notational point of view it is convenient to
-use the standard Western staff notes (c, d, e, ...) with
+use the standard Western staff notes (c, d, e, @dots{}) with
special accidentals that raise or lower notes by intervals
of 1/9, 4/9, 5/9 and 8/9 of a tone. These accidentals are
defined in the file @file{makam.ly}.
@itemize
@item
-the @code{<lilypond .... />} command, where you can directly enter short lilypond code
+the @code{<lilypond ... />} command, where you can directly enter short lilypond code
@item
the @code{<lilyond>...</lilypond>} environment, where you can directly enter longer
@unnumberedsubsec Error message Unbound variable %
This error message will appear at the bottom of the console
-output or log file together with a @qq{GUILE signalled an error ...}
+output or log file together with a @qq{GUILE signalled an error @dots{}}
message every time a Scheme routine is called which (invalidly)
contains a @emph{LilyPond} rather than a @emph{Scheme} comment.