> Is there any difference between the ASP page that reads from the DB and
> writes the XML and that backpage.asp that reads from the DB and writes
> the HTML output (which is UTF-8 encoded)? Are those ASP pages encoded
> with the same code page/encoding?


The backpage.asp - which reads the string from the DB and displays it -
has the meta tag on top:
<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">

The server page that prepares the XML (it is a single function called
on a server page), as well as the page that inserts it into the DB -
does not have any encoding directive.
None of the following:
Response.CharSet = "UTF-8"
Response.ContentType = "text/xml"
Response.CodePage = 65001


> How is the text stored in the DB, what DB is that, what column type is
> the text stored in?

The DB is Microsoft SQL Server 2000
The field is defined as nvarchar and when inserting the string into the
DB, through SP, I use
"adVarWChar" define.

BUT -
When adding Response.CodePage = 65001 to all server pages - I see the
Hebrew characters correctly.
Should I always add Response.CodePage = 65001 to server pages?
Should I leave the <meta HTTP-EQUIV="content-type" CONTENT="text/html;
charset=UTF-8"> for HTML pages?

Now, what I inserted previously looks like garbage, and the new posts
in Hebrew look OK (in the DB, in the XML and in the ASP pages).

I am confused. I don't know in which case I did right, and on which
case I did wrong...
What are the basic rules for UTF-8 support?

Thanks, Gabi.