html links updates

11 files changed, 25 insertions, 28 deletions

diff --git a/Doc/Manual/Android.html b/Doc/Manual/Android.html
index ae610b7d8..c90da21b4 100644
--- a/Doc/Manual/Android.html
+++ b/Doc/Manual/Android.html
@@ -47,7 +47,7 @@ This chapter contains a few Android specific notes and examples.
 
 
 <p>
-The examples require the <a href="http://developer.android.com/sdk/index.html">Android SDK</a> and <a href="http://developer.android.com/sdk/ndk/index.html">Android NDK</a> which can be installed as per instructions in the links.
+The examples require the <a href="http://developer.android.com/sdk/index.html">Android SDK</a> and <a href="http://developer.android.com/tools/sdk/ndk/index.html">Android NDK</a> which can be installed as per instructions in the links.
 The Eclipse version is not required for these examples as just the command line tools are used (shown for Linux as the host, but Windows will be very similar, if not identical in most places).
 Add the SDK tools and NDK tools to your path and create a directory somewhere for your Android projects (adjust PATH as necessary to where you installed the tools):
 </p>
diff --git a/Doc/Manual/CSharp.html b/Doc/Manual/CSharp.html
index e55013b1c..76590d1cc 100644
--- a/Doc/Manual/CSharp.html
+++ b/Doc/Manual/CSharp.html
@@ -70,7 +70,7 @@ SWIG C# works equally well on non-Microsoft operating systems such as Linux, Sol
 <p>
 To get the most out of this chapter an understanding of interop is required.
 The <a href="http://msdn.microsoft.com">Microsoft Developer Network (MSDN)</a> has a good reference guide in a section titled "Interop Marshaling".
-Monodoc, available from the Mono project, has a very useful section titled <a href="http://www.mono-project.com/Interop_with_Native_Libraries">Interop with native libraries</a>.
+Monodoc, available from the Mono project, has a very useful section titled <a href="http://www.mono-project.com/docs/advanced/pinvoke/">Interop with native libraries</a>.
 </p>
 
 <H3><a name="CSharp_introduction_swig2_compatibility"></a>20.1.1 SWIG 2 Compatibility</H3>
diff --git a/Doc/Manual/Introduction.html b/Doc/Manual/Introduction.html
index e0dd3c044..dc68bff43 100644
--- a/Doc/Manual/Introduction.html
+++ b/Doc/Manual/Introduction.html
@@ -383,7 +383,7 @@ for further information on this and other Autoconf macros.
 </p>
 
 <p>
-There is growing support for SWIG in some build tools, for example <a href="http://www.cmake.org">CMake</a>
+There is growing support for SWIG in some build tools, for example <a href="http://cmake.org">CMake</a>
 is a cross-platform, open-source build manager with built in support for SWIG. CMake can detect the SWIG executable
 and many of the target language libraries for linking against.
 CMake knows how to build shared libraries and loadable modules on many different operating systems.
diff --git a/Doc/Manual/Java.html b/Doc/Manual/Java.html
index b6885b94f..b953eb518 100644
--- a/Doc/Manual/Java.html
+++ b/Doc/Manual/Java.html
@@ -349,8 +349,6 @@ directory.   If that doesn't work, you will need to read the man-pages for
 your compiler and linker to get the right set of options.  You might also
 check the <a href="http://www.dabeaz.com/cgi-bin/wiki.pl">SWIG Wiki</a> for
 additional information.
-<a href="http://weblogs.java.net/blog/kellyohair/archive/2006/01/compilation_of.html">JNI compilation</a>
-is a useful reference for compiling on different platforms.
 </p>
 
 <p>
diff --git a/Doc/Manual/Javascript.html b/Doc/Manual/Javascript.html
index 613ca99ed..69e6665ea 100644
--- a/Doc/Manual/Javascript.html
+++ b/Doc/Manual/Javascript.html
@@ -166,7 +166,7 @@ $ make check-javascript-examples V8_VERSION=0x032530 ENGINE=v8</pre>
 <H3><a name="Javascript_node_extensions"></a>26.3.1 Creating node.js Extensions</H3>
 
 
-<p>To install <code>node.js</code> you can download an installer from their <a href="https://launchpad.net/~chris-lea/+archive/node.js">web-site</a> for Mac OS X and Windows. For Linux you can either build the source yourself and run <code>sudo checkinstall</code> or keep to the (probably stone-age) packaged version. For Ubuntu there is a <a href="https://launchpad.net/~chris-lea/+archive/node.js/">PPA</a> available.</p>
+<p>To install <code>node.js</code> you can download an installer from their <a href="https://launchpad.net/~chris-lea/+archive/node.js">web-site</a> for Mac OS X and Windows. For Linux you can either build the source yourself and run <code>sudo checkinstall</code> or keep to the (probably stone-age) packaged version. For Ubuntu there is a <a href="https://launchpad.net/~chris-lea/+archive/ubuntu/node.js/">PPA</a> available.</p>
 <div class="shell">
 <pre>
 $ sudo add-apt-repository ppa:chris-lea/node.js
diff --git a/Doc/Manual/Makefile b/Doc/Manual/Makefile
index d7011db06..7347691cd 100644
--- a/Doc/Manual/Makefile
+++ b/Doc/Manual/Makefile
@@ -34,14 +34,6 @@ check:
 	tidy -errors --gnu-emacs yes -quiet Sections.html
 	all=`sed '/^#/d' chapters | grep -v CCache.html`; for a in $$all; do tidy -errors --gnu-emacs yes -quiet $$a; done;
 
-# Check for links which don't work including those generated from the individual .html files into SWIGDocumentation.html
-linkchecker:
-	rm -rf linkchecker-tmp
-	mkdir linkchecker-tmp
-	cp SWIGDocumentation.html linkchecker-tmp
-	cp *.png linkchecker-tmp
-	(cd linkchecker-tmp && linkchecker -F text --no-warnings SWIGDocumentation.html)
-
 generate: swightml.book swigpdf.book
 	htmldoc --batch swightml.book || true
 	htmldoc --batch swigpdf.book || true
@@ -77,9 +69,18 @@ test:
 validate:
 	all=`sed '/^#/d' chapters`; for a in $$all; do validate --emacs $$a; done;
 
-# Link checking using linkchecker
-linkchecker:
+# Link checking using linkchecker of the index.html only file (including anchors)
+linkchecker1:
 	@echo -----------------------------------------------------------------------
 	@echo Note linkchecker versions prior to 6.1 do not work properly wrt anchors
 	@echo -----------------------------------------------------------------------
-	linkchecker --config=./linkchecker.config index.html
+	linkchecker --config=./linkchecker.config --anchors index.html
+
+# Check for links which don't work including those generated from the individual .html files into SWIGDocumentation.html
+linkchecker2:
+	rm -rf linkchecker-tmp
+	mkdir linkchecker-tmp
+	cp SWIGDocumentation.html linkchecker-tmp
+	cp *.png linkchecker-tmp
+	(cd linkchecker-tmp && linkchecker --config=../linkchecker.config -F text --no-warnings SWIGDocumentation.html)
+
diff --git a/Doc/Manual/Ocaml.html b/Doc/Manual/Ocaml.html
index da20b8da3..b927a7d8f 100644
--- a/Doc/Manual/Ocaml.html
+++ b/Doc/Manual/Ocaml.html
@@ -80,7 +80,7 @@ variants, functions, classes, etc.
 
 <p>
 If you're not familiar with the Objective Caml language, you can visit
-<a href="http://www.ocaml.org/">The Ocaml Website</a>.
+<a href="http://ocaml.org/">The Ocaml Website</a>.
 </p>
 
 <H2><a name="Ocaml_nn2"></a>31.1 Preliminaries</H2>
diff --git a/Doc/Manual/Preface.html b/Doc/Manual/Preface.html
index 23481d751..6ddea588a 100644
--- a/Doc/Manual/Preface.html
+++ b/Doc/Manual/Preface.html
@@ -370,7 +370,7 @@ installation of software you might have.  However, this is generally not the rec
 technique for building larger extension modules.  Instead, you should utilize
 Darwin's two-level namespaces.  Some details about this can be found here
 
-<a href="http://developer.apple.com/documentation/ReleaseNotes/DeveloperTools/TwoLevelNamespaces.html">http://developer.apple.com/documentation/ReleaseNotes/DeveloperTools/TwoLevelNamespaces.html</a>.
+<a href="https://developer.apple.com/library/mac/documentation/Porting/Conceptual/PortingUnix/compiling/compiling.html#//apple_ref/doc/uid/TP40002850-BCIHJBBF">Understanding Two-Level Namespaces</a>.
 
 </p>
 
diff --git a/Doc/Manual/Python.html b/Doc/Manual/Python.html
index 373472d86..962ee6843 100644
--- a/Doc/Manual/Python.html
+++ b/Doc/Manual/Python.html
@@ -2738,7 +2738,7 @@ in Python-2.2, an entirely new type of class system was introduced.
 This new-style class system offers many enhancements including static
 member functions, properties (managed attributes), and class methods.
 Details about all of these changes can be found on <a
-href="http://www.python.org">www.python.org</a> and is not repeated here.
+href="https://www.python.org">www.python.org</a> and is not repeated here.
 </p>
 
 <p>
@@ -5690,7 +5690,7 @@ import foo
 </div>
 <p>refers to a top-level module or to another module inside the current
 package. In Python 3 it always refers to a top-level module
-(see <a href="http://www.python.org/dev/peps/pep-0328/">PEP 328</a>).
+(see <a href="https://www.python.org/dev/peps/pep-0328/">PEP 328</a>).
 To instruct Python 2.5 through 2.7 to use new semantics (that is <tt>import
 foo</tt> is interpreted as absolute import), one has to put the following
 line
@@ -5881,7 +5881,7 @@ all overloaded functions share the same function in SWIG generated proxy class.
 
 <p>
 For detailed usage of function annotation, see
-<a href="http://www.python.org/dev/peps/pep-3107/">PEP 3107</a>.
+<a href="https://www.python.org/dev/peps/pep-3107/">PEP 3107</a>.
 </p>
 
 <H3><a name="Python_nn75"></a>36.12.2 Buffer interface</H3>
@@ -6074,7 +6074,7 @@ used to define an abstract base class for your own C++ class:
 
 <p>
 For details of abstract base class, please see
-<a href="http://www.python.org/dev/peps/pep-3119/">PEP 3119</a>.
+<a href="https://www.python.org/dev/peps/pep-3119/">PEP 3119</a>.
 </p>
 
 <H3><a name="Python_nn77"></a>36.12.4 Byte string output conversion</H3>
@@ -6160,7 +6160,7 @@ in Python 3 code.
 
 <p>
 For more details about the <tt>surrogateescape</tt> error handler, please see
-<a href="http://www.python.org/dev/peps/pep-0383/">PEP 383</a>.
+<a href="https://www.python.org/dev/peps/pep-0383/">PEP 383</a>.
 </p>
 
 </body>
diff --git a/Doc/Manual/Varargs.html b/Doc/Manual/Varargs.html
index dac1ad7bc..360bbaa12 100644
--- a/Doc/Manual/Varargs.html
+++ b/Doc/Manual/Varargs.html
@@ -605,7 +605,7 @@ you need to bring out some bigger guns.
 <p>
 One way to do this is to use a special purpose library such as libffi
 (<a
-href="http://sources.redhat.com/libffi/">http://sources.redhat.com/libffi</a>).
+href="http://www.sourceware.org/libffi/">http://www.sourceware.org/libffi/</a>).
 libffi is a library that allows you to dynamically construct
 call-stacks and invoke procedures in a relatively platform independent
 manner.  Details about the library can be found in the libffi
diff --git a/Doc/Manual/linkchecker.config b/Doc/Manual/linkchecker.config
index a947b278a..9317a8940 100644
--- a/Doc/Manual/linkchecker.config
+++ b/Doc/Manual/linkchecker.config
@@ -1,5 +1,3 @@
-[checking]
-anchors=1
-
 [filtering]
 ignorewarnings=http-robots-denied
+ignorewarnings=https-certificate-error