Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SamC
White Water Yakist
3467 Posts |
 Posted - 2003-07-18 : 11:27:22
|
| Yes, it's codepage, 65001.I use it in classis ASP to build Japanese HTML with charset UTF-8.I have no idea how to do the ASP.NET declaration of codepage 65001.Sam |
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2003-07-18 : 13:04:44
|
| Do you have Japanese (static/literal) text on the pages as well? So you must save the page as '.aspx with Unicode', and then the .NET platform amazingly takes care of setting the Request.codepage to 65001 when the page is served.Owais |
 |
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2003-07-18 : 17:25:44
|
| Could you post a sample snippet of the .net header?Sam |
|
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2003-07-19 : 03:09:26
|
| Sam, actually I was referring to the source code files of the aspx page. If you use the VS.NET IDE and you add a Web form to the project, if the page contains Unicode characters, VS.NET will automatically save the file with Unicode encoding, rather than the ANSI codepage of the Operating System. And when these pages are viewed in the browser the resulting HTML has its encoding set to Unicode. You can also do as Save As...and select Unicode .aspx from the dropdown list. I beleive it worked the same way with classic ASP as well. In any case, if you wish to set this property on the page, you can do it the same way it was done in classic asp:<@ Page Language="VB" CodePage="65001" EnableSessionState="True" %>Owais |
|
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2003-07-19 : 23:07:52
|
| Thanks. Seems clear enough now. It's working fine.Sam |
|
|
|
|
|
|
65001