468,247 Members | 1,310 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,247 developers. It's quick & easy.

PEAR::SOAP encoding issue

Hi all

I'm having some trouble with UTF8 / ISO-8859-1 encoding using a Webservice
based on PEAR::SOAP_Server. The client essentially sends an XML file as data
(i.e. XML-data wrapped in SOAP-XML envelope) to the server where it is
processed.

I've made sure the client sends data in ISO-8859-1, the XML data also has
this encoding set in the PI. However, the server seems to receive the data
as UTF8. Therefore, my german "umlaute" get all mangled up. Funny enough, it
seems if I run the client on an English Windows, the SOAP server gets UTF8,
if I run the same client (which sets the SOAP client encoding to ISO-8859-1
programmatically) on a German Windows, the encoding is ISO-8859-1 (statement
based on what mb_detect_encoding tells me).

Can someone enlighten me as to where encoding is important and I will have
to look into and where does it not matter.
- how do I force SOAP_Server to excpect ISO-8859-1 as request encoding?
$server->xml_encoding = 'ISO-8859-1'; ???
$server->response_encoding = 'ISO-8859-1'; ???
- are PHP internal strings always Unicode?
- how does domxml_open_mem work with encoding?

Thanks a lot
Simon
Feb 13 '06 #1
0 1145

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Arne Kösling | last post: by
reply views Thread by Jimmy Jim | last post: by
reply views Thread by Arne Kösling | last post: by
reply views Thread by Doug Farrell | last post: by
reply views Thread by Henrik Brautaset Aronsen | last post: by
3 posts views Thread by junkmail | last post: by
reply views Thread by Alexander Waldmann | last post: by
reply views Thread by Samuel Zallocco | last post: by
reply views Thread by wagemage.pt | last post: by
reply views Thread by info | last post: by
reply views Thread by NPC403 | last post: by
reply views Thread by zattat | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.