Both have the ASPCODEPAGE set to 65001 (utf-8) in the metabase. The
first server has been running pages like the one below for a long time
and the output has been correct ie. the ™ character and international
characters have displayed correctly (except that the ™ has never
displayed correctly in the titlebar). My problem is that the second
server is not displaying these characters correctly. Here's an example
of the asp code:
************************************************** *********************
<%@ Language=VBScript%>
<%Response.CharSet = "utf-8"%>
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8;">
<TITLE>Tradename™</TITLE>
</HEAD>
<body>
Nįttśruverndarsvęši Tradename™
</body>
</HTML>
************************************************** ***********************
The ™ displays as ? and the icelandic characters are garbled. If I
choose View > Encoding > Autoselect (turn off autoselect) and then View
Encoding > Autoselect (turn on autoselect) IE6 selects Western European rather than utf-8 and the page is correct (including the titlebar).
I have discovered that if I save the asp file as UTF-8 in notepad the
characters display correctly.
Here's the strange thing.. Although existing pages on the first server
are working fine, if I create the above test page these characters are
wrong on that server too. Once again if I save it as utf-8 it works. I
have opened some of the old pages in notepad and tried File > Save As
to see what their current encoding is and it is always ANSI, which
according to the new tests I'm running, should not work..
Also, if I copy a working page from server 1 to server 2 it doesnt work
on server 2 so it can't be the encoding of the file.
So my question is why would one page with the same character, the same
charset in the page and the same file encoding be rendered differently?
Is there a configuration setting I have missed that forces ASP pages to
be encoded in utf-8?
I would appreciate your comments.
Thanks
