How to UTF-8 encode a string?

[jens Jensen]

hello,
i'm doing utf-8 encoding the following way.
string message;

UTF8Encoding utf8 = new UTF8Encoding();

Byte[] encodedBytes = utf8.GetBytes(m essage);

message = encodedBytes.To String();

can someone correct me?

many thanks

JJ

[jens Jensen]

"Mike Schilling" <ap@newsgroup.n ospam> skrev i en meddelelse
news:uH******** ******@TK2MSFTN GP02.phx.gbl...

I am presuming that the problem is that the bytes are correct but the
remote service doesn't recognize them as being UTF-8. Try adding

req.ContentEnco ding = encoding;

My request object "req" does not seem to have seem to have "ContentEncodin g"
property.
I'm i missing something?

[Vadym Stetsyak]

Hello, jens!

try
req.ContentType = "text/xml; charset=utf-8";

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[jens Jensen]

> try

req.ContentType = "text/xml; charset=utf-8";

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

Hi Vadym,

I applied this, no chenge in the reponse from the server.

How can i actually dump the utf-8 encoded content to a file so i can see it
actually format following utf-8?

Many thanks

JJ

[Michael Voss]

Jon Skeet wrote:
[...snip...]

Note that you can use Encoding.UTF8En coding to avoid creating a new
instance each time.

[...snip...]

Would that code really create a new instance? I'd expect it to be a
Singleton or something like that, since it does not store any state
information.

[Vadym Stetsyak]

Hello, jens!

jJ> How can i actually dump the utf-8 encoded content to a file so i can
jJ> see it actually format following utf-8?

UTF8Encoding encoding = new UTF8Encoding();
byte[] postBytes = encoding.GetByt es(message);
req.ContentLeng th = postBytes.Lengt h;
System.IO.Strea m reqStream = req.GetRequestS tream();
reqStream.Write (postBytes, 0, postBytes.Lengt h);
reqStream.Close ();

System.IO.File. WriteAllBytes(p athHere, postBytes);


--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Vadym Stetsyak]

Hello, jens!

jJ> I applied this, no chenge in the reponse from the server.

What is server response? what error code? any content returned?

Another question if remote end is a webservice, why can't you make web reference to it and then communicate via stub?
--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Jon Skeet [C# MVP]]

Michael Voss wrote:

Jon Skeet wrote:
[...snip...]

Note that you can use Encoding.UTF8En coding to avoid creating a new
instance each time.

[...snip...]

Would that code really create a new instance? I'd expect it to be a
Singleton or something like that, since it does not store any state
information.

Using Encoding.UTF8En coding would reuse a single instance (I believe)
which is why I was suggesting using that instead of new UTF8Encoding().

Jon

[Nick Hounsome]

"Jon Skeet [C# MVP]" <sk***@pobox.co m> wrote in message
news:11******** *************@v 46g2000cwv.goog legroups.com...

Michael Voss wrote:

Jon Skeet wrote:
[...snip...]

> Note that you can use Encoding.UTF8En coding to avoid creating a new
> instance each time.

[...snip...]

Would that code really create a new instance? I'd expect it to be a
Singleton or something like that, since it does not store any state
information.

Using Encoding.UTF8En coding would reuse a single instance (I believe)
which is why I was suggesting using that instead of new UTF8Encoding().

Firstly there is no way to make "new X()" return an existing object because
unlike C++ you cannot override new so you can't do secret singletons.

Secondly the encoding does store 'state' information in the form of the
settings for BOM and exception throwing so in 1.1 there are 4 possible UTF8
encoding objects.

Worse, in 2.0 there is a settable EncoderFallback property which makes all
instances potentially unshareable. The work around for the static properties
is that they are all made readonly (IsReadOnly) and throw
InvalidOperatio nException if you try to set them. [It doesn't actually say
that in the documentation but it's the only sensible thing to do]

Also the static property is actually called Encoding.UTF8

[Nick Hounsome]

There is a serious documentation issue with the static encoding properties:

BOM and exception handling are undefined and therefore these properties are
not usable without firstly investigating their actual behaviour and secondly
taking it on faith that MS wont change it.

1) The documentaion should state what these are set to.
2) There should be properties to show these settings.
3) The documentation should state that they are readonly (in fact all
documentation should state the default value for all properties but it
rarely does)

In the absense of documentation the only easily maintainable way to go is to
always create your own using UTF8Encoding(bo ol,bool). The cost should be
trivial.

[Jon Skeet [C# MVP]]

Nick Hounsome wrote:

Using Encoding.UTF8En coding would reuse a single instance (I believe)
which is why I was suggesting using that instead of new UTF8Encoding().
Firstly there is no way to make "new X()" return an existing object because
unlike C++ you cannot override new so you can't do secret singletons.

Unless of course you're the CLR :)

(As discussed a short while ago, the System.String constructor returns
String.Empty in certain circumstances.)
Secondly the encoding does store 'state' information in the form of the
settings for BOM and exception throwing so in 1.1 there are 4 possible UTF8
encoding objects.
True - although it's not mutable state. It's not the kind of state
which prevents something being reused, let's say. (I want a word for
this kind of state - I've been using it a lot recently.)
Worse, in 2.0 there is a settable EncoderFallback property which makes all
instances potentially unshareable.
Aargh. I take back the above :)
The work around for the static properties
is that they are all made readonly (IsReadOnly) and throw
InvalidOperatio nException if you try to set them. [It doesn't actually say
that in the documentation but it's the only sensible thing to do]
Not sure what you mean - the Encoding.XXX properties? Or the properties
on the objects returned by the Encoding.XXX properties?
Also the static property is actually called Encoding.UTF8

Oops, yes.

Jon