Handling Foreign characters on Classic ASP pages

I am involved in building a web site that the foreign users with names containing foreign characters use to enter personal information. This information is either passed from page to page or entered into a database.
What can I do to prevent foreign characters from being converted to ASCIII code upon posting to other pages on the web site or writing to the database?
The web pages already have thi code:
         <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
How can I incorporate
                   <%@LANGUAGE="VBSCRIPT" CODEPAGE="65001"%>
the web server is already by default set to accept the web page language as VBSCRIPT.
Do I need to add Response.codepage to the web pages reciving the pieces user's information with foreign alphabets?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If you have those 2 tags then you're almost there, you just need to save the file as UTF8 format and you're all set. You can do this by opening the page in Notepad and go save-as.

/ Tobzzz

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Faye_DBAAuthor Commented:
Thanks, I will give a try.
Faye_DBAAuthor Commented:
Do you think you can lead me to an online knowledge Base to understand the procees why this is happening?
Maybe a book you know of about how to develope web site for international usage?

This is what one of the developers reported on this web site:

"But what is actually happening, on an inconsistent basis, is that a single character is being converted somewhere between when the data is submitted on one page and being retrieved on another, before the cleandata function is run. And this conversion is changing that single character to an HTML ampersand entity code (ñ converted to &#241;). This conversion adds characters to the data already checked for length, pushes the length over the limit (if the original value was already close), and causes multiple issues.

We need to figure out where and why this conversion is happening. Why is that conversion taking place before the data is retrieved on the page and the cleandata function is run"

Become a Microsoft Certified Solutions Expert

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

If all your pages are UTF8 with those tags in you need not convert any characters whatsoever. You do not need to clean/convert/change what's passed.
Faye_DBAAuthor Commented:
No the CleanData function is not for that purpose. It is rather for something else.
Is there some source online or in aook aout this?
Why are the characters getting converted?
I'm afraid I do not know of any reading material about this. Perhaps you could spend some time Googling "html foreign characters". Sorry I cannot be of more help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Development Software

From novice to tech pro — start learning today.