Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / March 2005

Tip: Looking for answers? Try searching our database.

WSE 2.0 and french text

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Sebastien Ollivier - 21 Mar 2005 13:01 GMT
I'm développing a C# Winform application that use PHP Web Services available
on an Apache HTTP Server.

These Web Services retrieve datas from an Oracle database.
These datas can be in french.
In French, special letters such as "é" or "è" are used.

I've generated a proxy wit WSE 2.0 and I'm using it to display my datas in a
ListBox.
Even if the special letters are in the Soap enveloppe of the HTTP Server
response, they are not displayed in my listbox.

For example, the Name "Stéphane" is displayed "Stphane".

If I generate a proxy without WSE 2.0 (without any other change in my
application), there is no problem. The text is correctly displayed.

Does anybody have an Idea ?
Yves Reynhout - 22 Mar 2005 22:21 GMT
> I'm développing a C# Winform application that use PHP Web Services available
> on an Apache HTTP Server.
[quoted text clipped - 14 lines]
>
> Does anybody have an Idea ?

This seems like an encoding issue. From what I remember you should use
UTF-8 encoding with WSE 2.0 (There's no support for any other form of
encoding).
Sebastien Ollivier - 23 Mar 2005 09:36 GMT
My Web Service is sending a response encoding with ISO-8859-1.
If i change the settings of my HTTP Server in order to send a response
encoded with UTF-8, an exception is thrown in my C# application because of an
"é" letter included in the soap enveloppe.
I think it's normal because "é" is not UTF-8.

Is there any way to enable ISO-8859-1 encoding in WSE 2.0 ?

> > I'm développing a C# Winform application that use PHP Web Services available
> > on an Apache HTTP Server.
[quoted text clipped - 18 lines]
> UTF-8 encoding with WSE 2.0 (There's no support for any other form of
> encoding).
Yves Reynhout - 23 Mar 2005 21:40 GMT
> My Web Service is sending a response encoding with ISO-8859-1.
> If i change the settings of my HTTP Server in order to send a response
[quoted text clipped - 3 lines]
>
> Is there any way to enable ISO-8859-1 encoding in WSE 2.0 ?
1. Does the SOAP response of your PHP web service specify the encoding
in the xml declaration (not as a HTTP header mind you)?

    <?xml version="1.0" encoding="ISO-8859-1"?>

2. If you have control over the PHP web services, change their encoding
to be UTF-8.
Sebastien Ollivier - 24 Mar 2005 12:17 GMT
That's what i did !! (read my previous messsage)
But it generates exception in the C# application.

I don't want to supress or convert the special letters.
I want to keep them in my c# application
That's why I would like to find a way that makes WSE 2.0 supporting them !!

> > My Web Service is sending a response encoding with ISO-8859-1.
> > If i change the settings of my HTTP Server in order to send a response
[quoted text clipped - 10 lines]
> 2. If you have control over the PHP web services, change their encoding
> to be UTF-8.
Yves Reynhout - 24 Mar 2005 13:50 GMT
You changed your http server's encoding settings, NOT the encoding of
the SOAP message (out on a limb here because I don't use Apache nor PHP
web services).

Your best chance to see what is going on is to use some kind of soap
trace tool to see what's crossing the wire encoding wise. (The full http
request/response, maybe you can post it in this forum (just trim the
data, we're only interested in the http headers and the soap specifics)).
Simon Fell @ http://www.pocketsoap.com has a number of trace tools you
can use.

OT: Using SoapEnvelope, you can specify the (request)encoding, by
manually setting the SoapEnvelope.Encoding property.
Sebastien Ollivier - 24 Mar 2005 16:31 GMT
In fact, I've changed both of them.
By default, th encoding is ISO-8859-1 in the soap Message (with NuSoap).
I can see it  using TCPMonitor (Axis) to see my request and my response
If y change the message encoding to UTF-8, the web service still send the
letters in the soap message.

But I don't think that the problem is on the server side.

The fact is that WSE2.0 doesn't support special letters and I would like it
to support them.

> You changed your http server's encoding settings, NOT the encoding of
> the SOAP message (out on a limb here because I don't use Apache nor PHP
[quoted text clipped - 9 lines]
> OT: Using SoapEnvelope, you can specify the (request)encoding, by
> manually setting the SoapEnvelope.Encoding property.
Yves Reynhout - 25 Mar 2005 00:50 GMT
> The fact is that WSE2.0 doesn't support special letters and I would like it
> to support them.
This is downright untrue. I can send you a project using both asmx and
WSE 2.0 (both client and server, both .NET), that can send é over UTF-8.
Drop me an email at yves.reynhout@nospam.com (replace the nospam with
ultragenda - just hate getting spam).
It has nothing todo with WSE 2.0, but with the encoding on your xml
payload and how your xml payload was encoded.

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.