From fb0fb710fff3fa2ec17bbb0df34b359ef016ee77 Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Thu, 1 Apr 2004 18:02:26 +0000 Subject: For some reason I decided it was better to say `output format' consistently in the documentation than to confuse matters by saying `back end'. One rogue back end removed. [originally from svn r4028] --- doc/input.but | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/input.but b/doc/input.but index e3849e3..25b6c3e 100644 --- a/doc/input.but +++ b/doc/input.but @@ -126,10 +126,10 @@ knows where the literal computer text starts and stops; and in plain text, this cannot be done by changing font, so there needs to be an alternative way. -So in the plain text back end, things marked as code (\c{\\c}) will -be surrounded by quote marks, so that it's obvious where they start -and finish. Things marked as weak code (\c{\\cw}) will not look any -different from normal text. +So in the plain text output format, things marked as code (\c{\\c}) +will be surrounded by quote marks, so that it's obvious where they +start and finish. Things marked as weak code (\c{\\cw}) will not +look any different from normal text. I recommend using weak code for any application where it is \e{obvious} that the text is literal computer input or output. For -- cgit v1.1