Mention our assumptions about the execution character set. Not very

well-written, since my brain is largely absent today.

git-svn-id: svn://svn.tartarus.org/sgt/putty@4945 cda61777-01e9-0310-a592-d414129be87e

diff --git a/doc/udp.but b/doc/udp.but
index 796b2c6..e5453ea 100644 (file)
--- a/doc/udp.but
+++ b/doc/udp.but
@@ -45,7 +45,10 @@ endianness-dependent operations, and so on.
 \e{don't} care about. In particular, we expect PuTTY to be compiled
 on 32-bit architectures \e{or bigger}; so it's safe to assume that
 \c{int} is at least 32 bits wide, not just the 16 you are guaranteed
-by ANSI C.)
+by ANSI C.  Similarly, we assume that the execution character encoding
+is a superset of the printable characters of ASCII, though we don't
+assume the numeric values of control characters, particularly \cw{'\n'}
+and \cw{'\r'}.)
 
 \H{udp-multi-backend} Multiple backends treated equally