]> git.donarmstrong.com Git - lilypond.git/commitdiff
Doc: CG: Fix backslashes in @samp example.
authorMark Polesky <markpolesky@yahoo.com>
Wed, 14 Apr 2010 07:33:49 +0000 (00:33 -0700)
committerMark Polesky <markpolesky@yahoo.com>
Wed, 14 Apr 2010 07:33:49 +0000 (00:33 -0700)
Documentation/contributor/doc-work.itexi

index e66e15476ecdc75f89383a9fca51398b60a7f868..c299d47d83f50672a4ab20ac1db15cab82fa3e1a 100644 (file)
@@ -590,17 +590,20 @@ blocks of @code{@@code}, @code{@@example}, or @code{@@verbatim}
 are not converted to left- and right-angled quotes
 (@code{@quoteleft{} @quoteright{}}) as they normally are within
 the text, so the apostrophes in
-@q{@w{@code{@@w@{@@code@{\relative c''@}@}}}} will display
+@q{@w{@code{@@w@{@@code@{@bs{}relative c''@}@}}}} will display
 correctly.  However, these settings do not affect the PDF output
 for anything within a @code{@@samp} block (even if it includes a
 nested @code{@@code} block), so entering
-@q{@code{@@w@{@@samp@{\relative c''@}@}}} wrongly produces
-@q{@w{@code{\relative c@quoteright{}@quoteright{}}}} in PDF.
+@q{@code{@@w@{@@samp@{@bs{}relative c''@}@}}} wrongly produces
+@q{@w{@code{@bs{}relative c@quoteright{}@quoteright{}}}} in PDF.
 Consequently, if you want to use a @code{@@samp@{@dots{}@}} block
 which contains backticks or apostrophes, you should instead use
 @q{@code{@@q@{@@code@{@dots{}@}@}}} (or
 @q{@code{@@q@{@@w@{@@code@{@dots{}@}@}@}}} if the block also
-contains spaces).
+contains spaces).  Note that backslashes within
+@code{@@q@{@dots{}@}} blocks must be entered as @samp{@@bs@{@}},
+so the example above would be coded as
+@q{@code{@@q@{@@w@{@@code@{@@bs@{@}relative c''@}@}@}}}.
 
 @item
 @code{@@command@{@dots{}@}} --- Use for command-line commands (eg.