From: Werner Lemberg Date: Mon, 26 Feb 2007 06:41:03 +0000 (+0100) Subject: Replace "..." with @q{...} where appropriate. X-Git-Tag: release/2.11.21-1~21 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=e45bd51e35dc2b13fe08b5b183b43c2019d7a95b;p=lilypond.git Replace "..." with @q{...} where appropriate. --- diff --git a/Documentation/user/advanced-notation.itely b/Documentation/user/advanced-notation.itely index 51911fe741..a5b33e360d 100644 --- a/Documentation/user/advanced-notation.itely +++ b/Documentation/user/advanced-notation.itely @@ -519,7 +519,7 @@ effect. In addition, vertical placement is performed after creating the text markup object. If you wish to move an entire piece of markup, -you need to use the #'padding property or create an "anchor" point +you need to use the #'padding property or create an @q{anchor} point inside the markup (generally with @code{\hspace #0}). @lilypond[quote,verbatim,fragment,relative=1] diff --git a/Documentation/user/converters.itely b/Documentation/user/converters.itely index 35cf314b20..6178d9a52e 100644 --- a/Documentation/user/converters.itely +++ b/Documentation/user/converters.itely @@ -96,7 +96,7 @@ Show summary of usage. @item -k, --key=@var{acc}[:@var{minor}] Set default key. @math{@var{acc} > 0} sets number of sharps; @math{@var{acc} < 0} sets number of flats. A minor key is indicated by -":1". +@samp{:1}. @item -o, --output=@var{file} Write output to @var{file}. diff --git a/Documentation/user/lilypond-book.itely b/Documentation/user/lilypond-book.itely index 543a4cdd42..3beacf52db 100644 --- a/Documentation/user/lilypond-book.itely +++ b/Documentation/user/lilypond-book.itely @@ -342,8 +342,8 @@ is trivial. @end example If a greater number of systems is requested, a TeX conditional must be -used before the @code{\endinput}. In this example, replace "2" by -the numer of systems you want in the output, +used before the @code{\endinput}. In this example, replace @q{2} by +the number of systems you want in the output, @example \def\betweenLilyPondSystem#1@{ diff --git a/Documentation/user/non-music.itely b/Documentation/user/non-music.itely index 790ecaa928..cf6f1a007c 100644 --- a/Documentation/user/non-music.itely +++ b/Documentation/user/non-music.itely @@ -405,7 +405,7 @@ option when invoking @code{lilypond --include=DIR} which adds DIR to the search path. The @code{\include} statement can use full path information, but with the Unix -convention @code{"/"} rather than the DOS/Windows @code{"\"}. For example, +convention @samp{/} rather than the DOS/Windows @samp{\}. For example, if @file{stuff.ly} is located one directory higher than the current working directory, use diff --git a/Documentation/user/programming-interface.itely b/Documentation/user/programming-interface.itely index 431e029919..7b59a3e8c5 100644 --- a/Documentation/user/programming-interface.itely +++ b/Documentation/user/programming-interface.itely @@ -785,8 +785,8 @@ add the marcato to its elements list property. (set! place new-value) @end example -Here, what we want to set (the "place") is the "elements" property of -@code{result-event-chord} expression +Here, what we want to set (the @q{place}) is the @q{elements} property of +@code{result-event-chord} expression. @example (ly:music-property result-event-chord 'elements) diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index b9dbf6853b..e152f21a94 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -134,8 +134,8 @@ The resulting PDF file will be displayed on your screen. Be warned that the first time you ever run LilyPond, it will take a minute or two because all of the system fonts have to be analyzed first. -For future use of LilyPond, you should begin by selecting "New" -or "Open". You must save your file before typesetting it. If any errors +For future use of LilyPond, you should begin by selecting @q{New} +or "@q{Open}. You must save your file before typesetting it. If any errors occur in processing, please see the log window. @subsubheading Windows diff --git a/Documentation/user/tweaks.itely b/Documentation/user/tweaks.itely index 0d48a53ee7..6d24d3a422 100644 --- a/Documentation/user/tweaks.itely +++ b/Documentation/user/tweaks.itely @@ -356,7 +356,7 @@ to understand these files. @file{@var{installdir}/LilyPond.app/Contents/Resources/share/lilypond/current/}. To access this, either @code{cd} into this directory from the Terminal, or control-click on the LilyPond application and select -"Show Package Contents". +@q{Show Package Contents}. @item Windows: @file{@var{installdir}/LilyPond/usr/share/lilypond/current/} diff --git a/Documentation/user/working.itely b/Documentation/user/working.itely index 9a3809d5c0..076bb6de00 100644 --- a/Documentation/user/working.itely +++ b/Documentation/user/working.itely @@ -382,8 +382,8 @@ tempoMark = #(define-music-function (parser location markp) (string?) That looks better, but let's make a few changes. The glissando is hard to see, so let's make it thicker and closer to the noteheads. Let's put the metronome marking above the clef, instead of over the first -note. And finally, my composition professor hates "C" time signatures, -so we'd better make that "4/4" instead. +note. And finally, my composition professor hates @q{C} time signatures, +so we'd better make that @q{4/4} instead. Don't change @file{music.ly}, though. Replace our @file{definitions.ly} with this: @@ -448,7 +448,7 @@ tempoMark = #(define-music-function (parser location markp) (string?) @end lilypond That looks nicer! But now suppose that I want to publish this -piece. My composition professor doesn't like "C" time +piece. My composition professor doesn't like @q{C} time signatures, but I'm somewhat fond of them. Let's copy the current @file{definitions.ly} to @file{web-publish.ly} and modify that. Since this music is aimed at producing a pdf which