why dont use CodePage = 65001 with utf-8 encoding
Printed From: Web Wiz Forums
Category: Web Wiz Web App Support Forums
Forum Name: Web Wiz Forums
Forum Description: Support forum for Web Wiz Forums application.
URL: https://forums.webwiz.net/forum_posts.asp?TID=29606
Printed Date: 01 April 2026 at 4:40am
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com
Topic: why dont use CodePage = 65001 with utf-8 encoding
Posted By: fooladi
Subject: why dont use CodePage = 65001 with utf-8 encoding
Date Posted: 04 August 2011 at 2:31pm
|
web wiz forum supports utf-8 but when open my access database Persian characters don't show correctly. solution is using: <% @ Language = VBScript CodePage = 65001%> instead of <% @ Language = VBScript %>. i don't know witch file must be edited but I change all files and it is now OK. please provide option for us because we use free edition and can not edit source code. or just ignore this kind of editing.  thanks |
Replies:
Posted By: fooladi
Date Posted: 04 August 2011 at 3:24pm
|
I find this answer in web and hope it be usefull: "The codepage 65001 does refer to the UTF-8 character set. You would need be make sure that your asp page (and any includes) are saved as UTF-8 if they contain any characters outside of the standard ASCII character set. By specifying the CODEPAGE attribute in the <%@ block you are indicating that anything written using Response.Write should be encoded to the Codepage specified, in this case 65001 (utf-8). Its worth bearing in mind that this does not affect any static content which is sent verbatim byte for byte to the response. Hence the reason why the file needs be actually saved using the codepage that is specified. The CharSet property of the response sets the CharSet value of the Content-Type header. This has no impact on how the content my be encoded it merely tells the client what encoding is being received. Again it is important that his value match the actual encoding sent." |
Posted By: WebWiz-Bruce
Date Posted: 05 August 2011 at 6:59am
|
Instead of changing the code page you need to be changing the LCID in the common.asp file. Open the common.asp file and at line 63 you will find:-
Change this to:-
The 1065 is for Persian (Iran) but other LCID's can be found on the http://www.webwiz.net/kb/asp-tutorials/date-time-settings.htm" rel="nofollow - LCID page . ------------- https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting |
Posted By: fooladi
Date Posted: 08 August 2011 at 12:26am
|
thanks. I enabled using of this line and correct session LCID on intact forum files on localhost. but this didn't work for me. (win7 x64 with Persian locality). in my database instead of: گل پروانه I see: Ú¯Ù„ پروانه so session CodePage = 65001 is only solution for me. |
Posted By: WebWiz-Bruce
Date Posted: 08 August 2011 at 7:36am
|
Check that you have set your database to use a collation that ius support by your language. After any changes to encodings, LCID, and collation you may find you need to re-save data again in your forum so that it is stored correctly. It maybe simpler to install again if your forum is new. ------------- https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting |