commit 293416828e1467f877d9dd928f174dcf81b103bc
author Daniel Veillard <veillard@redhat.com> Thu Sep 10 18:23:39 2009 +0200
committer Daniel Veillard <veillard@redhat.com> Thu Sep 10 18:23:39 2009 +0200
tree b4ebc11497be0e6aafc5824844bbb5cbf885feeb
parent d87c5d1c4fcd21641c66d93392d1761c2350f93b

Release of libxml2-2.7.4

* configure.in: new version
* libxml.spec.in: cleanup
* xmlregexp.c: fix a comment
* doc/apibuild.py: update
* doc/*: regenerate everything

doc/encoding.html

diff --git a/doc/encoding.html b/doc/encoding.html
index 1e3f0cc..387f6f3 100644
--- a/doc/encoding.html
+++ b/doc/encoding.html
@@ -33,7 +33,7 @@
 they are clearly labeled as such. For example the following is a wellformed
 XML document encoded in ISO-8859-1 and using accentuated letters that we
 French like for both markup and content:</p><pre>&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
-&lt;très&gt;là&lt;/très&gt;</pre><p>Having internationalization support in libxml2 means the following:</p><ul><li>the document is properly parsed</li>
+&lt;très&gt;là&lt;/très&gt;</pre><p>Having internationalization support in libxml2 means the following:</p><ul><li>the document is properly parsed</li>
   <li>information about it's encoding is saved</li>
   <li>it can be modified</li>
   <li>it can be saved in its original encoding</li>
@@ -51,7 +51,7 @@
   &lt;META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"&gt;
 &lt;/head&gt;
 &lt;body&gt;
-&lt;p&gt;W3C crée des standards pour le Web.&lt;/body&gt;
+&lt;p&gt;W3C crée des standards pour le Web.&lt;/body&gt;
 &lt;/html&gt;</pre><h3><a name="internal" id="internal">The internal encoding, how and why</a></h3><p>One of the core decisions was to force all documents to be converted to a
 default internal encoding, and that encoding to be UTF-8, here are the
 rationales for those choices:</p><ul><li>keeping the native encoding in the internal form would force the libxml
@@ -107,10 +107,10 @@
     You may end-up with a garbled document, or no document at all ! Example:
     <pre>~/XML -&gt; ./xmllint err.xml 
 err.xml:1: error: Input is not proper UTF-8, indicate encoding !
-&lt;très&gt;là&lt;/très&gt;
+&lt;très&gt;là&lt;/très&gt;
    ^
 err.xml:1: error: Bytes: 0xE8 0x73 0x3E 0x6C
-&lt;très&gt;là&lt;/très&gt;
+&lt;très&gt;là&lt;/très&gt;
    ^</pre>
   </li>
   <li>xmlSwitchEncoding() does an encoding name lookup, canonicalize it, and
@@ -163,10 +163,10 @@
     portability is really crucial</li>
 </ol><p>Here are a few examples based on the same test document:</p><pre>~/XML -&gt; ./xmllint isolat1 
 &lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
-&lt;très&gt;là&lt;/très&gt;
+&lt;très&gt;là&lt;/très&gt;
 ~/XML -&gt; ./xmllint --encode UTF-8 isolat1 
 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;très&gt;là  &lt;/très&gt;
+&lt;très&gt;là  &lt;/très&gt;
 ~/XML -&gt; </pre><p>The same processing is applied (and reuse most of the code) for HTML I18N
 processing. Looking up and modifying the content encoding is a bit more
 difficult since it is located in a &lt;meta&gt; tag under the &lt;head&gt;,