Fix NEWS file; update manual sources

[plcapi.git] / doc / xmlrpc_php.xml

diff --git a/doc/xmlrpc_php.xml b/doc/xmlrpc_php.xml
index 20c763f..e77df0a 100644 (file)
--- a/doc/xmlrpc_php.xml
+++ b/doc/xmlrpc_php.xml
@@ -8,10 +8,10 @@ PHP-XMLRPC User manual
 <book lang="en">
   <title>XML-RPC for PHP</title>
 
-  <subtitle>version 3.0.0</subtitle>
+  <subtitle>version 3.0.1</subtitle>
 
   <bookinfo>
-    <date>June 15, 2014</date>
+    <date>April 19, 2015</date>
 
     <authorgroup>
       <author>
@@ -212,6 +212,25 @@ PHP-XMLRPC User manual
     functions and methods please take a look at the source code of the
     library, which is quite thoroughly commented in javadoc-like form.</para>
 
+      <sect1>
+          <title>3.0.1</title>
+
+          <para><itemizedlist>
+              <listitem>
+                  <para>fixed: the library does not decode correctly LATIN-1 requests/responses if the character set is not set in the xml prolog</para>
+              </listitem>
+
+              <listitem>
+                  <para>fixed: the debugger sends incorrect requests when the payload includes LATIN-1 characters</para>
+              </listitem>
+
+              <listitem>
+                  <para>fixed: the client can not call remote methods which use LATIN-1 or UTF8 characters in their names</para>
+              </listitem>
+
+          </itemizedlist></para>
+      </sect1>
+
     <sect1>
       <title>3.0.0</title>
 
@@ -4097,7 +4116,7 @@ if (!$resp-&gt;faultCode())
       <para>PHP-XMLRPC only supports the ISO 8859-1 and UTF8 character sets.
       The net result of this situation is that those extra characters will not
       be properly encoded, and will be received at the other end of the
-      XML-RPC tranmission as "garbled data". Unfortunately the library cannot
+      XML-RPC transmission as "garbled data". Unfortunately the library cannot
       provide real support for CP1252 because of limitations in the PHP 4 xml
       parser. Luckily, we tried our best to support this character set anyway,
       and, since version 2.2.1, there is some form of support, left commented
@@ -4108,7 +4127,7 @@ if (!$resp-&gt;faultCode())
       <filename>xmlrpc.inc</filename> (you can search for the string "1252"),
       then set <code>$GLOBALS['xmlrpc_internalencoding']='CP1252';</code>
       Please note that all incoming data will then be fed to your application
-      as UTF-8 to avoid any potentail data loss.</para>
+      as UTF-8 to avoid any potential data loss.</para>
     </sect1>
 
     <sect1>