Roll libxml to bdec2183f34b37ee89ae1d330c6ad2bb4d76605f

third_party/libxml/src/win32/VC10/README.vc10

Index: third_party/libxml/src/win32/VC10/README.vc10
diff --git a/third_party/libxml/src/win32/VC10/README.vc10 b/third_party/libxml/src/win32/VC10/README.vc10
index f7826b0469a13d7d5f01652545137401b4071bc4..4805bdc8ad5cb1c66336625c86dbbe132ca0fb99 100644
--- a/third_party/libxml/src/win32/VC10/README.vc10
+++ b/third_party/libxml/src/win32/VC10/README.vc10
@@ -1,27 +1,27 @@
-
-README file for VC10 project files for libxml2
-----------------------------------------------
-
-to clarify: This is not the readme file for the whole libxml2 project. 
-Rather, it's a readme for the VC10 project files, attached to the libxml2 proejct.
-
-Quick Start
------------
-
-1) To use, load the libxml2.sln solution file into visual studio
-2) check and correct paths for dependent "iconv" project which most certaily 
-are wrong on your environment.
-3) Compile all projects
-
-
-Background Info
----------------
-
-Running of "configure.sh" won't make sense since VS doesn't support
-this kind of build system and the environment is pretty much known already 
-if you're using Visual Studio. Instead, a preconfigured "config.h" file 
-is provided in the "win32\VC10" directory and referenced by the project
-files already.
-
-The compile process is not completely warning-free: Some warnings will 
-appear during compile which can be ignored.
+
+README file for VC10 project files for libxml2
+----------------------------------------------
+
+to clarify: This is not the readme file for the whole libxml2 project. 
+Rather, it's a readme for the VC10 project files, attached to the libxml2 proejct.
+
+Quick Start
+-----------
+
+1) To use, load the libxml2.sln solution file into visual studio
+2) check and correct paths for dependent "iconv" project which most certaily 
+are wrong on your environment.
+3) Compile all projects
+
+
+Background Info
+---------------
+
+Running of "configure.sh" won't make sense since VS doesn't support
+this kind of build system and the environment is pretty much known already 
+if you're using Visual Studio. Instead, a preconfigured "config.h" file 
+is provided in the "win32\VC10" directory and referenced by the project
+files already.
+
+The compile process is not completely warning-free: Some warnings will 
+appear during compile which can be ignored.