tSpelling error "via." -> "via" corrected. - vaccinewars - be a doctor and try … | |
git clone git://src.adamsgaard.dk/vaccinewars | |
Log | |
Files | |
Refs | |
README | |
LICENSE | |
--- | |
commit a87c8d02c3c9251e2b38515344add2b01b7df011 | |
parent fe945a8d224e3644afbd7e697c6ef58fe29cf796 | |
Author: Ben Webb <[email protected]> | |
Date: Fri, 20 Dec 2002 13:17:22 +0000 | |
Spelling error "via." -> "via" corrected. | |
Diffstat: | |
M ChangeLog | 12 ++++++------ | |
M README | 4 ++-- | |
M doc/clientplay.html | 2 +- | |
M doc/configfile.html | 10 +++++----- | |
M doc/credits.html | 2 +- | |
M doc/metaserver.html | 6 +++--- | |
M doc/protocol.html | 2 +- | |
M doc/server.html | 2 +- | |
8 files changed, 20 insertions(+), 20 deletions(-) | |
--- | |
diff --git a/ChangeLog b/ChangeLog | |
t@@ -29,7 +29,7 @@ | |
removed - only an old client connecting to a new server will | |
trigger them) | |
- Bug fix: when the buttons in the Fight dialog are not visible to a | |
- mouse user, previously you were able to access them via. the keyboard | |
+ mouse user, previously you were able to access them via the keyboard | |
shortcuts; now fixed. | |
- configure should now work properly if GLib 2.0 is installed but | |
GTK2.0 is not | |
t@@ -113,7 +113,7 @@ | |
- Simple installer now in place for Win32 systems | |
1.5.1 19-06-2001 | |
- - Improved logging in server via. LogLevel and LogTimestamp variables | |
+ - Improved logging in server via LogLevel and LogTimestamp variables | |
- Metaserver (both client and server) moved to SourceForge | |
- Icons (courtesy of Ocelot Mantis) and GNOME desktop entry added | |
t@@ -139,7 +139,7 @@ | |
1.5.0beta1 08-04-2001 | |
- Completely rewritten fighting code | |
- Internationalization (i18n) support | |
- - Tense and case-sensitive translated strings handled via. dpg_ analogues | |
+ - Tense and case-sensitive translated strings handled via dpg_ analogues | |
to glib's g_ string handling functions %P = price, | |
%Txx or %txx = tense-sensitive string, %/.../ = comment (ignored) | |
- Networking revamped - now uses nonblocking sockets to improve server | |
t@@ -159,7 +159,7 @@ | |
client-specific code now placed in <xxx>_client.c, while generic code is | |
in message.c | |
- GTK+ client added | |
- - Native "pointy-clicky" Win32 graphical client added (via. GTK+ emulation) | |
+ - Native "pointy-clicky" Win32 graphical client added (via GTK+ emulation) | |
- GLib dependency introduced; string and list handling is taken care of | |
now by GLib routines | |
- Configuration files now handled by GLib's GScanner; "string lists" | |
t@@ -210,7 +210,7 @@ | |
- Option to allow the "local" server name to be specified when registering | |
with the metaserver - MetaServer.LocalName variable. Useful when the | |
metaserver refuses to resolve your IP address to your "preferred" domain | |
- name or when connecting via. an enforced web proxy. Email the metaserver | |
+ name or when connecting via an enforced web proxy. Email the metaserver | |
maintainer, for an authentication password (MetaServer.Password) linked … | |
your chosen domain name, to use this option successfully. | |
t@@ -243,7 +243,7 @@ | |
client to list the servers, prompt the user for a server, or play | |
in single-player mode, rather than connecting immediately to a server | |
- "MetaServer.Port" variable added to facilitate connection to the | |
- metaserver via. a proxy server (with thanks to Tony Brown) | |
+ metaserver via a proxy server (with thanks to Tony Brown) | |
- Signal handling cleaned up | |
- Buffer overflow problem with ExtractWord() fixed (hopefully) (with thanks | |
to Lamagra) | |
diff --git a/README b/README | |
t@@ -18,7 +18,7 @@ Either... | |
Or... | |
2. Get the tarball dopewars-1.5.8.tar.gz from the same URL | |
- Extract it via. tar -xvzf dopewars-1.5.8.tar.gz | |
+ Extract it via tar -xvzf dopewars-1.5.8.tar.gz | |
Follow the instructions in the INSTALL file in the newly-created | |
dopewars-1.5.8 directory | |
t@@ -76,7 +76,7 @@ settings in ~/.dopewars. All of the settings here can also b… | |
line of an interactive dopewars server when no players are logged on. See the | |
file "example-cfg" for an example configuration file, and for a brief | |
explanation of each option, type "help" in an interactive server. A subset of | |
-the configuration options can also be tweaked via. the "Options" menu item | |
+the configuration options can also be tweaked via the "Options" menu item | |
in the GTK+/Win32 client. | |
PLAYING | |
diff --git a/doc/clientplay.html b/doc/clientplay.html | |
t@@ -187,7 +187,7 @@ or if you attack other players.</p> | |
players, either human or computer-controlled. When joining a game which | |
already contains other players, they will be listed to you. Other players | |
which join or leave the game once you are playing will announce their | |
-presence to you automatically via. the "Messages" window.</p> | |
+presence to you automatically via the "Messages" window.</p> | |
<p>When in multiplayer mode, you can send a message to all current players by | |
pressing the "T" key from the main drug prices screen, and then typing in | |
diff --git a/doc/configfile.html b/doc/configfile.html | |
t@@ -111,7 +111,7 @@ accept connections coming in on any valid network interfac… | |
<dt><b>Socks.Active=<i>FALSE</i></b></dt> | |
<dd>Instructs the dopewars client to connect directly to the given server, | |
without using an intermediate SOCKS server. If this is set to TRUE, all | |
-connections go via. the SOCKS server. By default, SOCKS is not used for | |
+connections go via the SOCKS server. By default, SOCKS is not used for | |
metaserver communications - see the MetaServer.UseSocks variable. N.B. You | |
cannot run a dopewars server behind a SOCKS server, due to limitations in | |
the SOCKS protocol.</dd> | |
t@@ -199,15 +199,15 @@ This setting, if set to TRUE, can be overridden by the -S | |
<dd>Tells dopewars that the metaserver is located at | |
<i>dopewars.sourceforge.net</i>. See the | |
<a href="metaserver.html">metaserver</a> page, and below, for information | |
-about connecting to the dopewars metaserver via. a proxy web server.</dd> | |
+about connecting to the dopewars metaserver via a proxy web server.</dd> | |
<dt><b>MetaServer.Port=<i>80</i></b></dt> | |
<dd>Instructs dopewars that the metaserver can be found on TCP port | |
<i>80</i>. This is the standard HTTP port for Web access. (You shouldn't need | |
-to change this, even if you connect via. a proxy.)</dd> | |
+to change this, even if you connect via a proxy.)</dd> | |
<dt><b>MetaServer.ProxyName=<i>"proxy.com"</i></b></dt> | |
-<dd>Sends all requests to the metaserver via. the web proxy at <i>proxy.com</i… | |
+<dd>Sends all requests to the metaserver via the web proxy at <i>proxy.com</i>. | |
If this is set to a blank string (the default) then the connection to the | |
metaserver is made directly.</dd> | |
t@@ -229,7 +229,7 @@ maintained by the metaserver, to <i>dopewars server</i>.</… | |
<dt><b>MetaServer.LocalName=<i>"dope-serv.com"</i></b></dt> | |
<dd>Tells the metaserver that the preferred hostname of your dopewars server | |
machine is <i>dope-serv.com</i>. By default, the metaserver tries to ascertain | |
-your domain name from the connection, and this can fail if you connect via. | |
+your domain name from the connection, and this can fail if you connect via | |
a proxy server, or if DNS does not properly translate your IP address to your | |
domain name. You must also set MetaServer.Password to the password given to | |
you by the <a href="mailto:[email protected]">metaserver | |
diff --git a/doc/credits.html b/doc/credits.html | |
t@@ -46,7 +46,7 @@ as well as spotting many of his own and my bugs...</p> | |
<p><b>Matt Higgins</b> for a couple of patches to version 1.4.4.</p> | |
-<p><b>Tony Brown</b> for assistance with using dopewars via. enforced web | |
+<p><b>Tony Brown</b> for assistance with using dopewars via enforced web | |
proxies.</p> | |
<p><b>Leon Breedt</b> for writing a manpage, and creating a Debian package.</p> | |
diff --git a/doc/metaserver.html b/doc/metaserver.html | |
t@@ -34,7 +34,7 @@ pick the game that most suits them. This is the function of … | |
<h2><a id="location">Metaserver location</a></h2> | |
<p>The metaserver is a <a href="http://www.php.net/">PHP</a> script which lives | |
at <a href="http://sourceforge.net/">SourceForge</a>. It is accessed by both | |
-dopewars servers and clients via. TCP connection to port 80, by standard | |
+dopewars servers and clients via TCP connection to port 80, by standard | |
HTTP.</p> | |
<h2><a id="oldmeta">The "old" metaserver</a></h2> | |
t@@ -56,9 +56,9 @@ be working.</p> | |
<p>The metaserver, being an ordinary web page, should work happily on | |
most machines which have web access. A problem occurs, however, if your | |
-connection to the Web is via. an enforced proxy server (i.e. traffic on | |
+connection to the Web is via an enforced proxy server (i.e. traffic on | |
port 80 from your machine is blocked by firewall). dopewars can be | |
-configured to connect via. a proxy server without too much difficulty; if | |
+configured to connect via a proxy server without too much difficulty; if | |
your proxy server is at <i>proxy.com</i> on port <i>8080</i> then you should | |
add the following lines to your dopewars <a href="configfile.html"> | |
configuration file</a>:-<br /> | |
diff --git a/doc/protocol.html b/doc/protocol.html | |
t@@ -456,7 +456,7 @@ e.g. "^^Ar1010000" (N.B. the double ^ is a feature of the … | |
<h2><a id="refclient">Client to server message reference</a></h2> | |
<p>The messages are below are typically sent from the client to the server. No… | |
-that players do not communicate directly between each other, but always via. | |
+that players do not communicate directly between each other, but always via | |
the server. Note also that some of these messages are also valid when sent | |
from the server to the client.</p> | |
diff --git a/doc/server.html b/doc/server.html | |
t@@ -67,7 +67,7 @@ only run while you are logged on. As soon as you log out, th… | |
killed. To get around this limitation, dopewars supports being run as an | |
"NT Service" under Windows NT and later systems (e.g. 2000, XP). The install | |
program should set up the service; users with suitable access rights can then | |
-start or stop the service via. the Control Panel. The disadvantage of the | |
+start or stop the service via the Control Panel. The disadvantage of the | |
server in this configuration is that server commands cannot be issued once | |
the server is running. This limitation should be fixed in a future release | |
of dopewars.</p> |