[gtk+/gtk-2-24] Update README.win32 and Visual C++ Readme.txt's

[Chun-wei Fan <fanchunwei src gnome org>]

commit 92e632d525461fe2ea1a344a37ac3d0e87cf80fa
Author: Chun-wei Fan <fanchunwei src gnome org>
Date:   Wed Aug 31 14:53:24 2011 +0800

    Update README.win32 and Visual C++ Readme.txt's
    
    Tell people about the GNOME Live! page which gives a more
    detailed outline on building the GTK+ stack with Visual C++.

 README.win32                |   20 +++++++++++---------
 build/win32/vs10/README.txt |   11 +++++++----
 build/win32/vs9/README.txt  |   11 +++++++----
 3 files changed, 25 insertions(+), 17 deletions(-)
---
diff --git a/README.win32 b/README.win32
index 991aadf..7a8e852 100644
--- a/README.win32
+++ b/README.win32
@@ -156,15 +156,17 @@ Use the Microsoft compiler, cl and Make, nmake. Say nmake -f
 makefile.msc in gdk and gtk. Be prepared to manually edit various
 makefile.msc files, and the makefile snippets in build/win32.
 
-Since this release, there are also Visual Studio 9 (2008) and Visual
-Studio 10 (2010) Project Files that can be used to compile GTK+.
-They can be found in ./build/win32/vs9 and .build/win32/vs10 respectively
-for usage, and should build GTK+ out of the box provided the afore-mentioned
-compile-time dependencies are installed.  The VS2008/2010 Solution and
-Project files are currently maintained by Chun-wei Fan, and they currently
-build GDK with the Win32 backend, GTK+ and the gtk-demo demonstration program
-(GAIL and GAIL-utils are not built with this method yet).  Please see the
-READNE.txt file in ./build/win32/vs9 or ./build/win32/vs10 for more information.
+There are also VS 2008/2010 solution and project files to build GTK+, which
+are maintained by Chun-wei Fan. They should build GTK+ out of the box,
+provided that the afore-mentioned dependencies are installed. They will
+build GDK with the Win32 backend, GTK+ itself and the gtk-demo program.
+(The GAIL and GAIL-util sources are not built by this method yet)
+
+Please refer to the following GNOME Live! page for a more detailed ouline
+on the process of building the GTK+ stack and its dependencies with Visual
+C++:
+
+https://live.gnome.org/GTK%2B/Win32/MSVCCompilationOfGTKStack 
 
 Alternative 1 also generates Microsoft import libraries (.lib), if you
 have lib.exe available. It might also work for cross-compilation from
diff --git a/build/win32/vs10/README.txt b/build/win32/vs10/README.txt
index baae719..24b80b6 100644
--- a/build/win32/vs10/README.txt
+++ b/build/win32/vs10/README.txt
@@ -1,8 +1,11 @@
-Note that all this is rather experimental.
+Please do not compile this package (GTK+) in paths that contain
+spaces in them-as strange problems may occur during compilation or during
+the use of the library.
 
-Please do not compile GTK+ in a path that contains spaces, as this
-may cause problems during the build and/or during the use of the
-library.
+A more detailed outline for instructions on building the GTK+ with Visual
+C++ can be found in the following GNOME Live! page:
+
+https://live.gnome.org/GTK%2B/Win32/MSVCCompilationOfGTKStack 
 
 This VS10 solution and the projects it includes are intented to be used
 in a GTK+ source tree unpacked from a tarball. In a git checkout you
diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt
index 1386bde..cd73457 100644
--- a/build/win32/vs9/README.txt
+++ b/build/win32/vs9/README.txt
@@ -1,8 +1,11 @@
-Note that all this is rather experimental.
+Please do not compile this package (GTK+) in paths that contain
+spaces in them-as strange problems may occur during compilation or during
+the use of the library.
 
-Please do not compile GTK+ in a path that contains spaces, as this
-may cause problems during the build and/or during the use of the
-library.
+A more detailed outline for instructions on building the GTK+ with Visual
+C++ can be found in the following GNOME Live! page:
+
+https://live.gnome.org/GTK%2B/Win32/MSVCCompilationOfGTKStack 
 
 This VS9 solution and the projects it includes are intented to be used
 in a GTK+ source tree unpacked from a tarball. In a git checkout you