BUILD : 1.7.8 (588) BUGS : 304 NOTES : 1. nickIsServices() no longer alters the buffer 2. Fixes +I on Unreal and Bahamut 3. Anope Feature Request 285 4. Updates documentation 5. Ratbox compiles clean with make strict 6. Trap and storing of NICKCHARS

git-svn-id: svn://svn.anope.org/anope/trunk@588 31f1291d-b8d6-0310-a050-a5561fc1590b


git-svn-id: http://anope.svn.sourceforge.net/svnroot/anope/trunk@438 5417fbe8-f217-4b02-8779-1006273d7864

8 files changed, 55 insertions, 29 deletions

diff --git a/docs/DEFCON b/docs/DEFCON
index ba46744e8..1f5218d19 100644
--- a/docs/DEFCON
+++ b/docs/DEFCON
@@ -52,7 +52,7 @@ Anope DefCon
     Services will ignore everyone but opers           64 
     Services will silently ignore everyone but opers 128 
     AKILL all new clients trying to connect          256 
-    No new memos sent to block memoserv attacks      512
+    No new memos sent to block MemoServ attacks      512
 
     These are the values used to determine each defcon setting, are set via: 
 
diff --git a/docs/EVENTS b/docs/EVENTS
index 869257d31..d0695fd22 100644
--- a/docs/EVENTS
+++ b/docs/EVENTS
@@ -14,7 +14,7 @@ Anope Internal Events
     events such as the databases being saved. A list of triggered  events
     can be found below. Additional there is a module included with the core
     which can  provide some clue as to how to use the code in your modules.
-    The rest of this document assumes that you are used to writting modules.
+    The rest of this document assumes that you are used to writing modules.
 
 2) Complex Events
 
@@ -160,4 +160,8 @@ Anope Internal Events
     | EVENT_NICK_EXPIRE      | Nick of the account involved              |
     | EVENT_CHANGE_NICK      | Nick of the user involved                 |
     | EVENT_USER_LOGOFF      | Nick of the user involved                 |
+    | EVENT_GROUP            | Nick of the user involved                 |
+    | EVENT_NICK_IDENTIFY    | Nick of the user involved                 |
+    | EVENT_SERVER_SQUIT     | Name of the server involved               |
+    | EVENT_SERVER_CONNECT   | Name of the server involved               |
     |------------------------|-------------------------------------------|
diff --git a/docs/FAQ b/docs/FAQ
index fa042c779..d174568f7 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -86,7 +86,7 @@ Index:
 30. When I used the OperServ RAW command, Anope and/or my network
     crashed, or did weird things! Please fix this bug!
 
-31. I would like to have the list of the differents RAW on operserv
+31. I would like to have the list of the different RAW on OperServ
 
 32. I can't get /OS UMODES and /OS SVSNICK do not work!
 
@@ -116,9 +116,8 @@ Index:
 
 3. Does Anope run under Windows?
 
-	Well... not officially. Bu there is a port branch of services that will
-	work on Windows. Visit http://windows.anope.org for more information on
-    this port.
+	For more information visit http://windows.anope.org on how to obtain
+    the windows version of Anope.
 
 4. Can I send you questions without reading the FAQ, INSTALL or README 
    files?
@@ -391,7 +390,7 @@ Index:
 	be ignored, even if the problem happens not immediately.
 
 
-31. I would like to have the list of the different RAW on operserv
+31. I would like to have the list of the different RAW on OperServ
 
 	If you have to ask, you should not be messing with RAW :)
 
@@ -409,7 +408,7 @@ Index:
 	all channels. It must be activated on a per user basis and is
 	only available to Services Admins and Services Roots.
 	It is set using OperServ and is not persistent.
-	It only works if SuperAdmin is uncommented in the services
+	It only works if SuperAdmin is not commented in the services
 	configuration file. This is commented by default.
 	Read /msg OperServ HELP SET SUPERADMIN for further help.
 
diff --git a/docs/IRCD b/docs/IRCD
index ffa7873e8..6d2c5e5e3 100644
--- a/docs/IRCD
+++ b/docs/IRCD
@@ -19,12 +19,12 @@ How To Add IRCd Support
     C) Make a backup copy of Config and configure.in
 
     First step in this process is to rename the .c and .h file after the IRCd
-    that you are going to be adding support for. Its recommened that you come
+    that you are going to be adding support for. Its recommended that you come
     up with a name that is clear and easy to understand.
 
     Now that you have the files that you will need to create your own ircd
     support, starting with Config. This file is a shell script file; scroll
-    down untill you find the list of ircs for the user to select. Indicate
+    down until you find the list of ircs for the user to select. Indicate
     the based ircd version which is supported such as a series 1.x or 2.2.x,
     placing in the comment side an exact version that the support is for or
     "experimental" if you are not the ircd developer. The next step is to
@@ -32,7 +32,7 @@ How To Add IRCd Support
     'IRCTYPE_DEF="IRC_RATBOX"' to be the descriptive define for your ircd. 
 
     With the Config file ready to go, edit configure.in and find in there the
-    reference to --with-ircd. You should see see the various other ircds, and
+    reference to --with-ircd. You should see the various other ircds, and
     you will want to add yours in there using the same IRC_ name you came up
     with above. Important in this step is to make sure that you set the
     IRCDFILE to the name of the .c file you set in step 1. Once you have the
@@ -56,7 +56,7 @@ How To Add IRCd Support
 
     You are now ready to start getting into the code.
 
-2) Modifing the Header File
+2) Modifying the Header File
 
     Now that you have gotten past the first part of the creation process, you
     are into the code. This part is the harder and more complex part. You
@@ -101,7 +101,7 @@ How To Add IRCd Support
 
     Finally we come to DEFAULT_MLOCK; this is the mode that services will set
     by default on channels when they are registered. In general you want this
-    to be whats acceptable by the ircd; in most cases this is "+nt"
+    to be what is acceptable by the ircd; in most cases this is "+nt"
 
 3) The Code
 
@@ -246,10 +246,10 @@ How To Add IRCd Support
                               opped (+o), and protected (+a) on IRCd's that
                               support it.
 
-    24) SVSNICK: Can the ircd use SVSNICK to change someones nick? Otherwise,
+    24) SVSNICK: Can the ircd use SVSNICK to change some ones nick? Otherwise,
                  KILL is used. Use 1 for yes, 0 for no.
 
-    25) VHOST: Can a user's host be changd on the fly? Enabling this allow
+    25) VHOST: Can a user's host be changed on the fly? Enabling this allow
                HostServ online. Use 1 for yes, 0 for no.
 
     26) OWNER: Has a channel umode for being the channel owner. For example,
@@ -283,7 +283,7 @@ How To Add IRCd Support
 
     34) SZLINE: Does the IRCd support SZLINES? Use 1 for yes, 0 for no.
 
-    35) HALFOP: Is channelmode +h for halfop supported by the IRCd? Use 1 for
+    35) HALFOP: Is channel mode +h for halfop supported by the IRCd? Use 1 for
                 yes, 0 for no.
 
     36) Number of Server Args: When an IRCd connects, this is the number of
@@ -336,7 +336,7 @@ How To Add IRCd Support
     51) vIdent: Support for including a user's ident in their vHost. Use
                 1 for yes, 0 for no.
 
-    52) SVSHOLD: Support for temporarely 'holding' a nick, instead of using
+    52) SVSHOLD: Support for temporarily 'holding' a nick, instead of using
                  a nick enforcer client. Use 1 for yes, 0 for no.
 
     53) TS on MODE: We need to send a timestamp when modes are being changed.
@@ -395,7 +395,7 @@ How To Add IRCd Support
     71) Tokens: Can we use tokens to talk to the IRCd? Use 1 for yes,
                 0 for no.
 
-    72) Token Case Senstive: Are the IRCd's TOKENS/COMMANDS case senstive?
+    72) Token Case Senstive: Are the IRCd's TOKENS/COMMANDS case sensitive?
                              Use 1 for yes, 0 for no.
 
     73) base64 SJOIN TS: Are the timestamps sent with a SJOIN in base64? Use
@@ -411,7 +411,7 @@ How To Add IRCd Support
     77) SVSMODE UCMODE: Can we clear user channel modes with SVSMODE? Use
                         1 for yes, 0 for no.
 
-    78) SGline Enforce: Does the IRCd enfore SGLINES for us or do we need to
+    78) SGline Enforce: Does the IRCd enforce SGLINES for us or do we need to
                         do so? Use 1 for yes, 0 for no.
 
     79) Vhost Character: The character used to represent the vHost mode, if
@@ -424,6 +424,9 @@ How To Add IRCd Support
 
     82) P10: Is this IRCd a P10-style IRCd? Use 1 for yes, 0 for no.
 
+    83) Character Set: Unreal passes the character set during PROTOCTL,
+                       the value is stored here. Set this NULL to start.
+
     So we've had this long list. Now there's a second struct to fill. This
     struct isn't as long as the previous one though, so we'll handle it quite
     quick compared to the previous one.
@@ -465,6 +468,10 @@ How To Add IRCd Support
     CAPAB_UMODE2    | 0x02000000 | UMODE2    | Supports UMODE2 command
     CAPAB_VL        | 0x04000000 | VL        | VLine information in info field
     CAPAB_TLKEXT    | 0x08000000 | TLKEXT    | Not 8, but 10 params in TKL's
+    CAPAB_CHANMODE  | 0x10000000 | CHANMODE  | Channel modes are passed here
+    CAPAB_SJB64     | 0x20000000 | SJB64     | SJOIN timestamps are base64 encoded
+    CAPAB_NICKCHARS | 0x40000000 | NICKCHARS | Character set used by the IRCD for nicks
+
 
 4) Modes 
 
@@ -479,6 +486,22 @@ How To Add IRCd Support
     place the UMODE_i into this slot. Your base .c file should contain a good
     start for this, as well as a little help locating the characters.
 
+	The following mode set is for the channel symbols. During a SJOIN event 
+    the modes are sent usually before the nick. These normally are @, +, %
+    etc.. depending on the ircd. Starting at ASCII 0 and running to 127. 
+    Replace the 0 with the character (o = @, h = %) for the given mode. In the
+    case of halfop which is usually sent as % replace the 37th character with
+    'h', do this until all modes that are possible be received in this manor 
+    have been inserted into the array.
+
+	Now that you have that complete, the following array is ready to be dealt
+    with. This is the cmmodes array, like the others it is a ASCII array
+	starting at 0 and going to 127. However at the given letter you will want
+    to enter the add, and delete function for the given mode. In the case of
+    bans (+b) there is add_ban, and del_ban. Anope provides functions for 
+    bans, exceptions and invites, should your ircd have more then these please
+    contact Anope to discuss what can be done to add this mode.
+
 5) Functions and Events
 
     A brief word about functions and events. All events are captured using:
diff --git a/docs/MODULES b/docs/MODULES
index 85fb283d5..98e0026af 100644
--- a/docs/MODULES
+++ b/docs/MODULES
@@ -79,7 +79,7 @@ Anope Modules
 
 5) More Modules
 
-    Anope ships with two sample modules that only illustrates some of the
+    Anope ships with three sample modules that only illustrates some of the
     implemented module capabilities. They don't really do much or anything
     useful.
 
diff --git a/docs/NEWS b/docs/NEWS
index f6aabec87..619379903 100644
--- a/docs/NEWS
+++ b/docs/NEWS
@@ -1,6 +1,6 @@
 Highlighted News in Anope 1.6
 =============================
-  * Fixed various exploits and vulverabilities.
+  * Fixed various exploits and vulnerabilities.
   * Fixed various language typos and inconsistencies.
   * Improved ignore system.
   * Improved ./configure script.
@@ -41,7 +41,7 @@ After the change from Epona to Anope
   * Services realtime logging to a channel
   * SuperAdmin directive for access to "super" commands.
   * Ban system is now exception aware.
-  * HostServ for hostname masquarading.
+  * HostServ for hostname masquerading.
   * Smarter XOP System.
   * Email verification/handshake upon registration.
   * Services can now /ignore users.
@@ -86,7 +86,7 @@ while networks using UnrealIRCd must upgrade to Unreal 3.1.1.
 
 For the full changes, see the Changes file.
 
-For announcements and discussions about Anope, subscribe to the mailing
-list by sending an e-mail to epona-request@epona.org with "subscribe"
-in the body (quotes excluded). You can then post to the mailing list
-by sending an e-mail to epona@epona.org.
+For announcements and discussions about Anope, please visit our
+web site http://www.anope.org
+
+
diff --git a/docs/README b/docs/README
index ab9968a6f..ff4b47fa0 100644
--- a/docs/README
+++ b/docs/README
@@ -3,7 +3,7 @@ Anope -- a set of IRC services for IRC networks
 
 Anope is          2003-2005 Anope Team    <info@anope.org>.
 Based on Epona    2000-2002 PegSoft       <epona@pegsoft.net>.
-Based on Services 1996-1999 Andrew Church <achurch@dragonfire.net>.
+Based on Services 1996-1999 Andrew Church <achurch@achurch.org>.
 
 This program is free but copyrighted software; see the file COPYING for
 details.
diff --git a/docs/WIN32.txt b/docs/WIN32.txt
index 5afc7553c..d743be716 100644
--- a/docs/WIN32.txt
+++ b/docs/WIN32.txt
@@ -83,7 +83,7 @@ Anope for Windows
  
     4) You are now ready to compile. bring up the Visual C++ toolkit command
        prompt; This will launch a dos command prompt like windows, which will
-       set the enviroment properties need to make Anope. Change directories
+       set the environment properties need to make Anope. Change directories
        to where you unpacked the source code in step 2. At the prompt type:
 
         nmake -f Makefile.win32
@@ -102,7 +102,7 @@ Anope for Windows
 2) Installation
 
     Since Anope for Windows does not use a visual interface, you must do the
-    configuration with a texteditor before proceeding with running anope
+    configuration with a text editor before proceeding with running anope
     itself.
 
     Open services.conf, and read through it carefully and adjust the settings