X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Fudp.but;h=c50464ee14991b3720d6fbf8974f724098e00396;hb=145ecf611238c4f1e39d89d3eee40319a2c54fe8;hp=e5453ea0b98a052d9b2dca034bae663f7c202317;hpb=3d3273337c962c1911c72ff549ae719e54c5833e;p=PuTTY.git

diff --git a/doc/udp.but b/doc/udp.but
index e5453ea0..c50464ee 100644
--- a/doc/udp.but
+++ b/doc/udp.but
@@ -3,8 +3,6 @@
 \# PuTTY's `unwritten design principles'. It has nothing to do with
 \# the User Datagram Protocol.
 
-\define{versionidudp} \versionid $Id$
-
 \A{udp} PuTTY hacking guide
 
 This appendix lists a selection of the design principles applying to
@@ -45,10 +43,12 @@ 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.  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'}.)
+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'}. Also, the X forwarding code
+assumes that \c{time_t} has the Unix format and semantics, i.e. an
+integer giving the number of seconds since 1970.)
 
 \H{udp-multi-backend} Multiple backends treated equally