UTF-8 and Server.URLEncod e

[burnsy2000]

We are running ASP classic on IIS 5 on W2k SP4. We recently added <%
Response.charse t="utf-8"%to the top of all our pages (as suggested by
validator.w3.or g). A problem arose on a page which applies
Server.HTMLEnco de to a field that was inputted from the user. The
problem is that when the user enters a phrase such as:

My Fiancé

The Server.URLEncod e returns the value:

My Fiancé

which doesn't appear correct. When I take out the <%
Response.charse t="utf-8"%line, it returns

My Fiancé

which displays correctly. Am i ok to just leave out the <%
Response.charse t="utf-8"%line, or should I use a different charset?
or is there some other fix?

[Anthony Jones]

>>>

"burnsy2000 " <mc*******@gigm asters.comwrote in message
news:11******** *************@s 34g2000cwa.goog legroups.com...
We are running ASP classic on IIS 5 on W2k SP4. We recently added <%
Response.charse t="utf-8"%to the top of all our pages (as suggested by
validator.w3.or g).
<<<

You also require Session.CodePag e = 65001.

>>>

A problem arose on a page which applies
Server.HTMLEnco de to a field that was inputted from the user. The
problem is that when the user enters a phrase such as:

My Fiancé

The Server.URLEncod e returns the value:

My Fiancé

<<<

I think you are confusing URLEncode with HTMLEncode. The output is
consistent with HTMLEncode. What you are seeing here is the posted form
data being formatted as UTF-8 but being read by the server as 1252 (or
whatever your default OEM codepage is).

>>>

which doesn't appear correct. When I take out the <%
Response.charse t="utf-8"%line, it returns

My Fiancé

which displays correctly. Am i ok to just leave out the <%
Response.charse t="utf-8"%line, or should I use a different charset?
or is there some other fix?
<<<
If you ensure ALL pages Begin with Session.CodePag e = 65001 and
Response.CharSe t = "UTF-8" your problems should go away. (Note if you have
been saving results of form posts to a DB you may well have corrupt entiries
in your DB)

Anthony.