French characters in query string

[darin dimitrov]

Hello,

How can I convert an url encoded string containing some french
characters back to the original string?

I have the following html form:
<form>
name = <input type="text" name="name" value="Noël Pirès"/>
<input type="submit" value="OK"/>
</form>

When I submit this form the following data is sent at protocol level
using HTTP GET: name=No%EBl+Pir %E8s

I tried converting it with the HttpUtility.Url Decode method in order
to obtain the original string but with no success. This method
returned
"name=Nol Pirs" and the special french characters are omitted. What
function should I use in order to decode such a string.

In fact I would like to implement the following: I have a text file
containing the urlencoded string and in a console application I want
to make the conversion, something like:

------------------------
FileStream fin = new FileStream(@"c: \test.txt", FileMode.Open,
FileAccess.read );
byte[] buf = new byte[fin.Length];
fin.Read(buf, 0, (int)buf.Length );
string s = Encoding.Defaul t.GetString(buf );

s = HttpUtility.Url Decode(s);
System.Console. Write(s);
------------------------

and the test.txt file:
------------------------
name=No%EBl+Pir %E8s
------------------------
Any suggestions?

[Jon Skeet [C# MVP]]

darin dimitrov <da************ @hotmail.com> wrote:

How can I convert an url encoded string containing some french
characters back to the original string?

As far as I know, there's not much in the way of standardisation for
what URL encodings mean above the top of ASCII. The most robust way of
proceeding, IMO, is to use post data instead.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[darin dimitrov]

Jon Skeet [C# MVP] <sk***@pobox.co m> wrote in message news:<MP******* *************** **@msnews.micro soft.com>...

darin dimitrov <da************ @hotmail.com> wrote:

How can I convert an url encoded string containing some french
characters back to the original string?

As far as I know, there's not much in the way of standardisation for
what URL encodings mean above the top of ASCII. The most robust way of
proceeding, IMO, is to use post data instead.

I will post the solution I found myself in case that someone else
might be interested:

The problem was that when I use the HttpUtility.Url Decode methode
there is no way to specify the encoding, so instead I used the
HttpUtility.Url DecodeToBytes method like:

<code>
string s = "name=No%EBl+Pi r%E8s";
byte[] binaryData = HttpUtility.Url DecodeToBytes(s ,
Encoding.Defaul t);
s = Encoding.Defaul t.GetString(bin aryData);
</code>

Now s = "name=Noël Pirès"

[Jon Skeet [C# MVP]]

darin dimitrov <da************ @hotmail.com> wrote:

As far as I know, there's not much in the way of standardisation for
what URL encodings mean above the top of ASCII. The most robust way of
proceeding, IMO, is to use post data instead.

I will post the solution I found myself in case that someone else
might be interested:

The problem was that when I use the HttpUtility.Url Decode methode
there is no way to specify the encoding, so instead I used the
HttpUtility.Url DecodeToBytes method like:

<code>
string s = "name=No%EBl+Pi r%E8s";
byte[] binaryData = HttpUtility.Url DecodeToBytes(s ,
Encoding.Defaul t);
s = Encoding.Defaul t.GetString(bin aryData);
</code>

Now s = "name=Noël Pirès"

That's fine so long as you know that the client was using the same
encoding - but do you?

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[darin dimitrov]

Jon Skeet [C# MVP] <sk***@pobox.co m> wrote in message news:<MP******* *************** **@msnews.micro soft.com>...

darin dimitrov <darin di******@hotmai l.com> wrote:

As far as I know, there's not much in the way of standardisation for
what URL encodings mean above the top of ASCII. The most robust way of proceeding, IMO, is to use post data instead.

I will post the solution I found myself in case that someone else
might be interested:

The problem was that when I use the HttpUtility.Url Decode methode
there is no way to specify the encoding, so instead I used the
HttpUtility.Url DecodeToBytes method like:

<code>
string s = "name=No%EBl+Pi r%E8s";
byte[] binaryData = HttpUtility.Url DecodeToBytes(s ,
Encoding.Defaul t);
s = Encoding.Defaul t.GetString(bin aryData);
</code>

Now s = "name=No l Pir s"

That's fine so long as you know that the client was using the same
encoding - but do you?

In my particular case I know the encoding that my clients are using,
but I agree that this is not a general solution. I would appreciate
any better suggestions.

[Jon Skeet [C# MVP]]

darin dimitrov <da************ @hotmail.com> wrote:

That's fine so long as you know that the client was using the same
encoding - but do you?

In my particular case I know the encoding that my clients are using,
but I agree that this is not a general solution. I would appreciate
any better suggestions.

As I said before, a much better way of passing data is in the body of
the request, as that has an encoding associated with it.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too