From 26a81bc286deb48556f557985c6a806b948fac9d Mon Sep 17 00:00:00 2001 From: Mark Polesky Date: Wed, 9 Jul 2014 14:40:31 -0700 Subject: [PATCH] Mention backslash escaping in Scheme. Clarify confusion about `@code{\foo}' vs. `@code{\\foo}'. --- Documentation/contributor/doc-work.itexi | 12 ++++++++++++ 1 file changed, 12 insertions(+) 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 -- 2.39.2