point to mailing list page instead of listing email addresses

Few more HTML corrections


git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@6082 626c5289-ae23-0410-ae9c-e8d60b6d4f22

SWIG/Doc/Manual/CSharp.html

@@ -137,7 +137,7 @@ Visual Studio .NET 2003 solution and project files are available for compiling w
 If your SWIG installation went well on a Unix environment and your C# compiler was detected, you should be able to type <tt>make</tt> in each example directory, 
 then <tt>ilrun runme</tt> (Portable.NET C# compiler) or <tt>mono runme</tt> (Mono C# compiler) to run the examples.
 Windows users can also get the examples working using a
-<a href="http://www.cygwin.com">Cygwin</a> or <a href=http://www.mingw.org>MinGW</a> environment for automatic configuration of the example makefiles.
+<a href="http://www.cygwin.com">Cygwin</a> or <a href="http://www.mingw.org">MinGW</a> environment for automatic configuration of the example makefiles.
 Any one of the three C# compilers (Portable.NET, Mono or Microsoft) can be detected from within a Cygwin or Mingw environment if installed in your path. 
 
 </body>

SWIG/Doc/Manual/Makefile

@@ -53,3 +53,6 @@ test:
 	  grep "href=\".*\.html\"" Sections.html
 	  all=`sed '/^#/d' chapters`; for a in $$all; do grep -l "href=\".*\.html\"" $$a; done;
 
+validate:
+	  all=`sed '/^#/d' chapters`; for a in $$all; do /home/william/builds/wdg_validate/validate --emacs $$a; done;
+

SWIG/Doc/Manual/Modula3.html

@@ -419,8 +419,8 @@ Is it possible to sub-class C++ classes with Modula-3 code?
 This issue is addressed by directors,
 a feature that was experimentally added to some Language modules
 like
-<a href=Java.html#java_directors>Java</a> and
-<a href=Python.html#directors>Python</a>.
+<a href="Java.html#java_directors">Java</a> and
+<a href="Python.html#directors">Python</a>.
 </li>
 <li>
 How to manage storage with the garbage collector of Modula-3?

SWIG/Doc/Manual/Perl5.html

@@ -551,7 +551,7 @@ source has a list of macros that are known to conflict with either standard head
 other headers.  But if you get macro type conflicts from other macros not included
 in Lib/perl5/noembed.h while compiling the wrapper, you will
 have to find the macro that conflicts and add an #undef into the .i file.  Please report
-any conflicting macros you find to <a href="mailto:swig@cs.uchicago.edu">swig@cs.uchicago.edu</a>.
+any conflicting macros you find to <a href="http://www.swig.org/mail.html">swig mailing list</a>.
 
 <H3><a name="Perl5_nn10"></a>22.2.7 Compiling for 64-bit platforms</H3>
 

SWIG/Doc/Manual/Preface.html

@@ -196,8 +196,8 @@ port.
 Although every attempt has been made to make SWIG bug-free, we are also trying
 to make feature improvements that may introduce bugs.
 To report a bug, either send mail to the SWIG developer
-list at <tt>swig-dev@cs.uchicago.edu</tt> or report a bug
-at <tt>http://www.swig.org</tt>. In your report, be as specific as
+list at the <a href="http://www.swig.org/mail.html">swig-dev mailing list</a> or report a bug
+at the <a href="http://www.swig.org/bugs.html">SWIG bug tracker</a>. In your report, be as specific as
 possible, including (if applicable), error messages, tracebacks (if a
 core dump occurred), corresponding portions of the SWIG interface file
 used, and any important pieces of the SWIG generated wrapper code.  We

SWIG/Doc/Manual/SWIG.html

@@ -2617,7 +2617,8 @@ In the process of building an interface, SWIG may encounter syntax errors or
 other problems.  The best way to deal with this is to simply copy the offending
 code into a separate interface file and edit it.   However, the SWIG developers
 have worked very hard to improve the SWIG parser--you should report parsing errors
-to <tt>swig-dev@cs.uchicago.edu</tt> or to the SWIG bug tracker on <tt>www.swig.org</tt>.
+to the <a href="http://www.swig.org/mail.html">swig-dev mailing list</a> or to the 
+<a href="http://www.swig.org/bugs.html">SWIG bug tracker</a>.
 </p>
 
 <H3><a name="SWIG_nn47"></a>5.7.2 The SWIG interface file</H3>

SWIG/Doc/Manual/SWIGPlus.html

@@ -1506,8 +1506,8 @@ rule for 'int').
 This error means that the target language module supports overloading,
 but for some reason there is no type-checking rule that can be used to
 generate a working dispatch function.  The resulting behavior is then
-undefined.  You should report this as a bug to
-<tt>swig-dev@cs.uchicago.edu</tt>.
+undefined.  You should report this as a bug to the
+<a href="http://www.swig.org/bugs.html">SWIG bug tracking database</a>.
 
 <p>
 If you get an error message such as the following,
@@ -1661,7 +1661,7 @@ members (of all classes):
 Note: the <tt>*::</tt> syntax is non-standard C++, but the '*' is meant to be a
 wildcard that matches any class name (we couldn't think of a better
 alternative so if you have a better idea, send email to
-swig-dev@cs.uchicago.edu).
+the <a href="http://www.swig.org/mail.html">swig-dev mailing list</a>.
 
 <p>
 Although this discussion has primarily focused on <tt>%rename</tt> all of the same rules

SWIG/Doc/Manual/Typemaps.html

@@ -1,3 +1,4 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>
 <head>
 <title>Typemaps</title>

SWIG/Doc/Manual/Windows.html

@@ -160,7 +160,7 @@ If you do not have access to Visual C++ you will have to set up project files /
 <H2><a name="Windows_nn13"></a>3.3 SWIG on Cygwin and MinGW</H2>
 
 
-SWIG can also be compiled and run using <a href="http://www.cygwin.com">Cygwin</a> or <a href=http://www.mingw.org>MinGW</a> which provides a Unix like front end to Windows and comes free with gcc, an ANSI C/C++ compiler. However, this is not a recommended approach as the prebuilt executable is supplied. 
+SWIG can also be compiled and run using <a href="http://www.cygwin.com">Cygwin</a> or <a href="http://www.mingw.org">MinGW</a> which provides a Unix like front end to Windows and comes free with gcc, an ANSI C/C++ compiler. However, this is not a recommended approach as the prebuilt executable is supplied. 
 
 <H3><a name="swig_exe"></a>3.3.1 Building swig.exe on Windows</H3>