From: Werner Lemberg Date: Sun, 25 Sep 2011 06:40:04 +0000 (+0200) Subject: [doc] Use @dots{} where appropriate. X-Git-Tag: release/2.15.13-1~10 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=7ae1e99ff67432c96faf743bc28ac7b90a47a852;p=lilypond.git [doc] Use @dots{} where appropriate. --- diff --git a/Documentation/learning/fundamental.itely b/Documentation/learning/fundamental.itely index b203fefd6e..ae7b467c25 100644 --- a/Documentation/learning/fundamental.itely +++ b/Documentation/learning/fundamental.itely @@ -943,7 +943,7 @@ Notation Reference: @ruser{Multiple voices}. 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. diff --git a/Documentation/notation/simultaneous.itely b/Documentation/notation/simultaneous.itely index e287bde6ac..8f55aea928 100644 --- a/Documentation/notation/simultaneous.itely +++ b/Documentation/notation/simultaneous.itely @@ -304,7 +304,7 @@ voices in a single staff is illustrated in the following example: @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 @@ -382,7 +382,7 @@ The first example could be typeset as follows: 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, diff --git a/Documentation/notation/spacing.itely b/Documentation/notation/spacing.itely index 37557fcb2d..4c7ab5b008 100644 --- a/Documentation/notation/spacing.itely +++ b/Documentation/notation/spacing.itely @@ -3275,7 +3275,7 @@ Snippets: @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. diff --git a/Documentation/notation/world.itely b/Documentation/notation/world.itely index 1863feb7cd..cdc2b0fe30 100644 --- a/Documentation/notation/world.itely +++ b/Documentation/notation/world.itely @@ -532,7 +532,7 @@ Western scales and modes: @notation{koma} (1/9 of a tone), @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}. diff --git a/Documentation/usage/lilypond-book.itely b/Documentation/usage/lilypond-book.itely index 2b00f57cc4..93cfec3fd5 100644 --- a/Documentation/usage/lilypond-book.itely +++ b/Documentation/usage/lilypond-book.itely @@ -498,7 +498,7 @@ music in HTML files: @itemize @item -the @code{} command, where you can directly enter short lilypond code +the @code{} command, where you can directly enter short lilypond code @item the @code{...} environment, where you can directly enter longer diff --git a/Documentation/usage/running.itely b/Documentation/usage/running.itely index 147bc84c67..c14d8c51b6 100644 --- a/Documentation/usage/running.itely +++ b/Documentation/usage/running.itely @@ -823,7 +823,7 @@ mismatched quote will usually be on the line one or two above. @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.