diff options
author | Mark Polesky <markpolesky@yahoo.com> | 2014-07-09 14:40:31 -0700 |
---|---|---|
committer | Mark Polesky <markpolesky@yahoo.com> | 2014-07-15 23:03:44 -0700 |
commit | 26a81bc286deb48556f557985c6a806b948fac9d (patch) | |
tree | 80f561c6a6d538ae6dde9ae625d4c750abfd6d58 | |
parent | 85530210e95f55885e6b472e753b7561739fa472 (diff) |
Mention backslash escaping in Scheme.
Clarify confusion about `@code{\foo}' vs. `@code{\\foo}'.
-rw-r--r-- | Documentation/contributor/doc-work.itexi | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/Documentation/contributor/doc-work.itexi b/Documentation/contributor/doc-work.itexi index 7bf37c72e9..cdd069ed5d 100644 --- a/Documentation/contributor/doc-work.itexi +++ b/Documentation/contributor/doc-work.itexi @@ -945,6 +945,18 @@ the same format as @code{@@enumerate}. Do not use @node Special characters @unnumberedsubsubsec Special characters +@warning{In Texinfo, the backslash is an ordinary character, and +is entered without escaping (e.g. +@samp{The@tie{}@@code@{@bs{}foo@}@tie{}command}). However, within +double-quoted Scheme and/or LilyPond strings, backslashes +(including those ending up in Texinfo markup) need to be escaped +by doubling them: +@example +(define (foo x) + "The @@code@{@bs{}@bs{}foo@} command..." + ...) +@end example} + @itemize @item @code{--}, @code{---} --- Create an en dash (--) or an em dash |