Faye_DBA
asked on
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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 ñ). 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"
Thanks
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 ñ). 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"
Thanks
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.
ASKER
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?
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.
ASKER