From 0c4ba28a316e3c9c48bf52db3d2081634a8e61f7 Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Sat, 12 Jun 2004 21:57:29 +0000 Subject: Er, don't forget to document the disallowing of \q within \c. Ahem. [originally from svn r4278] --- doc/input.but | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/input.but b/doc/input.but index 6cb1808..1c20acc 100644 --- a/doc/input.but +++ b/doc/input.but @@ -202,10 +202,12 @@ ASCII one if they aren't available. But I recommend using the built-in \c{\\q} command in most cases, because it's simple and does the best it can everywhere. -(Note that if you're using the \c{\\c} or \c{\\cw} commands to -display literal computer code, you probably \e{will} want to use -literal \i{ASCII quote characters}, because it is likely to matter -precisely which quote character you use.) +If you're using the \c{\\c} or \c{\\cw} commands to display literal +computer code, you will probably want to use literal \i{ASCII quote +characters}, because it is likely to matter precisely which quote +character you use. In fact, Halibut actually \e{disallows} the use +of \c{\\q} within either of \c{\\c} and \c{\\cw}, since this +simplifies some of the output formats. \S{input-nonbreaking} \c{\\-} and \c{\\_}: \ii{Non-breaking hyphens} and \I{non-breaking spaces}spaces -- cgit v1.1