fix SWIG naming convention

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

Doc/Manual/Allegrocl.html

@@ -14,7 +14,7 @@
 <ul>
 <li><a href="#Allegrocl_nn2">Basics</a>
 <ul>
-<li><a href="#Allegrocl_nn3">Running Swig</a>
+<li><a href="#Allegrocl_nn3">Running SWIG</a>
 <li><a href="#Allegrocl_nn4">Command Line Options</a>
 <li><a href="#Allegrocl_nn5">Inserting user code into generated files</a>
 </ul>
@@ -138,7 +138,7 @@ to it.
 <H2><a name="Allegrocl_nn2"></a>17.1 Basics</H2>
 
 
-<H3><a name="Allegrocl_nn3"></a>17.1.1 Running Swig</H3>
+<H3><a name="Allegrocl_nn3"></a>17.1.1 Running SWIG</H3>
 
 
 <p>

Doc/Manual/CSharp.html

@@ -55,7 +55,7 @@ The PInvoke interface has been chosen over Microsoft's Managed C++ interface as
 PInvoke is part of the ECMA/ISO C# specification.
 It is also better suited for robust production environments due to the Managed C++ flaw called the
 <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vcconMixedDLLLoadingProblem.asp">Mixed DLL Loading Problem</a>.
-Swig C# works equally well on non-Microsoft operating systems such as Linux, Solaris and Apple Mac using
+SWIG C# works equally well on non-Microsoft operating systems such as Linux, Solaris and Apple Mac using
 <a href="http://www.mono-project.com/">Mono</a> and <a href="http://www.dotgnu.org/pnet.html">Portable.NET</a>.
 </p>
 

Doc/Manual/Contents.html

@@ -537,7 +537,7 @@
 <ul>
 <li><a href="Allegrocl.html#Allegrocl_nn2">Basics</a>
 <ul>
-<li><a href="Allegrocl.html#Allegrocl_nn3">Running Swig</a>
+<li><a href="Allegrocl.html#Allegrocl_nn3">Running SWIG</a>
 <li><a href="Allegrocl.html#Allegrocl_nn4">Command Line Options</a>
 <li><a href="Allegrocl.html#Allegrocl_nn5">Inserting user code into generated files</a>
 </ul>

Doc/Manual/Guile.html

@@ -814,7 +814,7 @@ Produces the following code at the top of the generated GOOPS guile-module
 <code>Module-primitive.scm</code> (with <i>primitive</i> replaced with whatever is given with the <code>-primsuffix</code>
 argument.  The code to load the <code>.so</code> library should be located in the <code>%scheme</code> directive, 
 which will then be added to the scmstub file.
-Swig will automatically generate the line <code>(use-modules (<i>Package</i> <i>Module-primitive</i>))</code>
+SWIG will automatically generate the line <code>(use-modules (<i>Package</i> <i>Module-primitive</i>))</code>
 into the GOOPS guile-module.  So if <i>Module-primitive.scm</i> is on the autoload path for guile, the
 <code>%goops</code> directive can be empty.  Otherwise, the <code>%goops</code> directive should contain 
 whatever code is needed to load the <i>Module-primitive.scm</i> file into guile.</p>
@@ -848,7 +848,7 @@ Produces the following code at the top of the generated GOOPS guile-module
 </li>
 
 <li><p><b>Module Linkage</b>: This is very similar to passive linkage with a scmstub file.
-Swig will also automatically generate the line <code>(use-modules 
+SWIG will also automatically generate the line <code>(use-modules 
 (<i>Package</i> <i>Module-primitive</i>))</code> into the GOOPS guile-module.  Again the <code>%goops</code>
 directive should contain whatever code is needed to get that module loaded into guile.</p>
 

Doc/Manual/Perl5.html

@@ -112,7 +112,7 @@ options are found near the end of the chapter.
 
 
 <p>
-To build a Perl5 module, run Swig using the <tt>-perl</tt> option as
+To build a Perl5 module, run SWIG using the <tt>-perl</tt> option as
 follows :
 </p>
 

Doc/Manual/Php.html

@@ -101,7 +101,7 @@ also contain PHP5 class wrappers.
 </p>
 
 <p>
-Swig can generate PHP extensions from C++ libraries as well when
+SWIG can generate PHP extensions from C++ libraries as well when
 given the <tt>-c++</tt> option.  The support for C++ is discussed in
 more detail in <a href="#Php_nn2_6">section 27.2.6</a>.
 </p>

Doc/Manual/Python.html

@@ -1137,7 +1137,7 @@ simply represented as opaque values using an especial python container object:
 
 <div class="targetlang"><pre>
 &gt;&gt;&gt; print f
-&lt;Swig Object at _08a71808_p_FILE&gt;
+&lt;Swig Object of type 'FILE *' at 0xb7d6f470&gt;
 </pre></div>
 
 <p>
@@ -1147,7 +1147,7 @@ dereference the pointer from Python. Of course, that isn't much of a concern in
 </p>
 
 <p>
-In older versions of Swig (1.3.22 or older), pointers were represented
+In older versions of SWIG (1.3.22 or older), pointers were represented
 using a plain string object. If you have an old package that still
 requires that representation, or you just feel nostalgic, you can
 always retrieve it by casting the pointer object to a string:
@@ -1171,7 +1171,7 @@ integer:
 
 <p>
 However, the inverse operation is not possible, i.e., you can't build
-a Swig pointer object from a raw integer value.
+a SWIG pointer object from a raw integer value.
 </p>
 
 <p>

Doc/Manual/Ruby.html

@@ -7097,7 +7097,7 @@ being created. </div>
 with Ruby objects. The following functions may prove to be useful.
 (These functions plus many more can be found in <a href="http://www.rubycentral.com/book"><em>Programming
 Ruby</em></a>, by David Thomas and Andrew Hunt.)&nbsp;</p>
-<p>In addition, we list equivalent functions that Swig defines, which
+<p>In addition, we list equivalent functions that SWIG defines, which
 provide a language neutral conversion (these functions are defined for
 each swig language supported). &nbsp;If you are trying to create a swig
 file that will work under multiple languages, it is recommended you
@@ -7123,7 +7123,7 @@ across multiple languages.</p>
   <tbody>
     <tr>
       <th style="font-weight: bold;">RUBY</th>
-      <th style="font-weight: bold;">Swig</th>
+      <th style="font-weight: bold;">SWIG</th>
       <td></td>
     </tr>
     <tr>

Doc/Manual/SWIGPlus.html

@@ -3471,7 +3471,7 @@ instead:
 
 <p>
 In this case, the default and conversion constructors have the same
-name. Hence, Swig will overload them and define an unique visible
+name. Hence, SWIG will overload them and define an unique visible
 constructor, that will dispatch the proper call depending on the argument
 type.
 </p>