git://git.onelab.eu
/
plcapi.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
9b4a6c2
)
Fix tzo typos in the manual
author
gggeek
<giunta.gaetano@gmail.com>
Sat, 6 Dec 2014 23:13:11 +0000
(23:13 +0000)
committer
gggeek
<giunta.gaetano@gmail.com>
Sat, 6 Dec 2014 23:13:11 +0000
(23:13 +0000)
doc/xmlrpc_php.xml
patch
|
blob
|
history
diff --git
a/doc/xmlrpc_php.xml
b/doc/xmlrpc_php.xml
index
20c763f
..
a37fc21
100644
(file)
--- a/
doc/xmlrpc_php.xml
+++ b/
doc/xmlrpc_php.xml
@@
-4097,7
+4097,7
@@
if (!$resp->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
<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 tran
s
mission 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
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
+4108,7
@@
if (!$resp->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
<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 potent
ai
l data loss.</para>
+ as UTF-8 to avoid any potent
ia
l data loss.</para>
</sect1>
<sect1>
</sect1>
<sect1>