@CODEPAGE

The @CODEPAGE processing directive specifies how literal (static) strings are encoded in a Web page. A code page is a character set, which can include numbers, punctuation marks, and other glyphs. Codepages are not the same for each language. Some languages, such as Japanese and Hindi, have multibyte characters, while others, such as English and German, only need one byte to represent each character. The @CODEPAGE processing directive is write-only.

A code page can be represented in a table as a mapping of characters to single-byte values or multibyte values. Many code pages share the ASCII character set for characters in the range 0x00-0x7F.

Syntax

<%@ CODEPAGE = codepage%>

Parameters

codepage

An unsigned integer that represents a valid code page for the system that is running the ASP scripting engine.

Remarks

Setting @CODEPAGE explicitly affects literal strings in a single response. Response.CodePage affects dynamic strings in a single response, and Session.CodePage affects dynamic strings in all responses in a session.

If @CODEPAGE is not explicitly set in a page, it is implicitly set by the AspCodePage metabase property or by the system ANSI code page.

There can be only one code page per response body, otherwise incorrect characters are displayed. If you set the code page explicitly in two pages, where one is called by the other by using #include, Server.Execute, or Server.Transfer, usually the parent page decides the code page. The only exception is if Response.CodePage is explicitly set in the parent page of a Server.Execute call. In this case, an @CodePage command in the child page overrides the parent code page.

If you set Response.CodePage or Session.CodePage explicitly, do so before sending non-literal strings to the client. If you use literal and non-literal strings in the same page, make sure the code page of @CODEPAGE matches the code page of Response.CodePage, or the literal strings are encoded differently from the non-literal strings and display incorrectly.

If the code page of your Web page matches the system defaults of the Web client, you do not need to set a code page in your Web page. However, setting the value is recommended.

If the code page is set in a page, then Response.Charset should also be set. The code page value specifies to IIS how to encode the data when building the response, and the charset value tells the browser how to decode the data when displaying the response. The CharsetName of Response.Charset must match the code page value, or mixed characters are displayed in the browser. Lists of CharsetNames and matching code page values can be found on MSDN Web Workshop under the columns for Preferred Charset Label and FamilyCodePage.

The file format of a Web page must be the same as the @CODEPAGE used in the page. Notepad enables you to save files in UTF-8 format or in the system ANSI format. For example, if @CODEPAGE is set to 65001 for UTF-8, the Web file must be saved in UTF-8 format. If @CODEPAGE is set to 1252, the Web file must be saved in ANSI format on an English or German system. If you want to save a page in the ANSI format for a language other than your system language, you can change your default System Locale settings in Regional and Language Options on the Control Panel. For example, after you change your system locale to Japanese, any files you save in ANSI format are saved using the Japanese code page and are only readable from a Japanese system locale.

If you are writing and testing Web pages that use different code pages and character sets (for example, if you are creating a multilingual Web site), remember that your test client computer must have the language packs installed for each language you want to display. You can install language packs from Regional and Language Options on the Control Panel.

Example Code

For more information, see the example for Response.CodePage.

Requirements

Client: Requires Windows XP Professional, Windows 2000 Professional, or Windows NT Workstation 4.0.

Server: Requires Windows Server 2003, Windows 2000 Server, or Windows NT Server 4.0.

Product: IIS

See Also

Reference

Session.CodePage

Response.CodePage

asp关于从utf8页面到gb2312页面出现乱码得解决

昨天做了两个asp页面,一个是utf-8得页面一个则是gb2312得页面.

于是发生了件怪事(主要是我第一次遇见得),单独打开这两个页面都不会出现问题,

但偏偏从utf8连接到gb2312得时候就出现了乱码.花了两个小时都搞不掉,

今天再次打开,baidu了下结果.

后来发现两个解决方案

第一:在每个gb2312页面上设置Session.CodePage=936

这样问题就解决了...

第二:从utf8转到gb2312得时候不要用<a>连接.用response.redirect跳转,也能解决.

综上,我理解为

给每个页面设置CodePage这样就把各个页面得编码都独立起来,不再受相连页面得影响

其次<a>标签连接会将页面编码属性也传递给下一个页面,而使用redirect就不会出现这样得情况了,这跟

用asp得环境变量取Request.ServerVariables("HTTP_REFERER")一样,后者就取不到.

另附上

对于ASP编码问题的深入研究与最终解决方案

哪的资料都不如官方资料权威。今天总算从MSDN中择出了ASP编码问题的解决方案。

下面是MSDN中的一段话。

Setting @CODEPAGE explicitly affects literal strings in a single response. Response.CodePage affects dynamic strings in a single response, and Session.CodePage affects dynamic strings in all responses in a session.

这句话解释清楚了@CODEPAGE，Response.CodePage，Session.CodePage 分别的作用是什么。

@CODEPAGE作用于所有静态的字符串，比如某文件中的 const blogname="我的家"

Response.CodePage,Session.CodePage作用于所有动态输出的字符串，比如<%=blogname%>

这句话很关键的是说明了Response.CodePage的作用范围是a single response，而SXNA中声明的Session.CodePage的作用范围是all responses in a session。

再看另外一句话。

If Response.CodePage is not explicitly set in a page, it is implicitly set by Session.CodePage, if sessions are enabled. If sessions are not enabled, Response.CodePage is set by @CodePage, if @CodePage is present in the page. If there is no @CodePage in the page, Response.CodePage is set by the AspCodePage metabase property. If the AspCodePage metabase property is not set, or set to 0, Response.CodePage is set by the system ANSI code page.

这句话我乍一看，把意思理解成了这样：在sessions are enabled的时候，如果Response.CodePage没有声明，则Response.CodePage会被Session.CodePage赋值。如果sessions are not enabled的时候, 如果@CodePage已声明，则Response.CodePage会被@CodePage赋值，等等.............

这句话解释了为什么从SXNA中出来以后进入一些别的页面比如oblog,z-blog等等容易出现乱码，因为其他程序没有声明Response.CodePage而恰巧SXNA声明了Session.CodePage，因此一进入SXNA，Session.CodePage立即被赋值（版本不同，有的版本赋了936有的版本赋了65001），而后进入其他程序的时候Response.CodePage马上被Session.CodePage赋值，如果这时Response.CodePage与页面本身编码不一样的话，页面就会出现乱码。所以进入z-blog出现乱码的时候我查了当时的Session.CodePage和Response.CodePage都是936，而进入oblog出现乱码的时候Session.CodePage和Response.CodePage都是65001.就是说要想保证叶面不出现乱码，应该声明Response.CodePage，否则他就会按照Session.CodePage来解释网页（而不是按照@codepage解释网页）.

如果仅仅按照上面的解释的话，我实际上是很糊涂的，因为我们都是用的中文操系统，当每一次进入浏览器的时候你可以尝试输出Session.CodePage，能看到他都是936！为什么进入Z-blog的时候他不把默认的Session.CodePage的936赋给Response.CodePage呢？反而把@CodePage给了Response.CodePage？什么情况下Session.CodePage才赋值给Response.CodePage呢？原文的sessions are enabled应该如何理解呢？

也许上面的话应该这样理解：

在Session.CodePage被任何程序声明的时候，如果Response.CodePage没有声明，则Response.CodePage会被Session.CodePage赋值。如果Session.CodePage没有被任何程序声明的时候, 如果@CodePage已声明，则Response.CodePage会被@CodePage赋值，....，最后的页面动态内容部分按照Response.CodePage的值解释。

因为Zblog和Oblog都声明了@CodePage，所以，用户刚刚启动完机器然后进入浏览器浏览Zblog和Oblog的时候Response.CodePage会被@CodePage赋值，于是叶面显示正常。

这句话进一步解释了产生乱码的原因

If you set Response.CodePage or Session.CodePage explicitly, do so before sending non-literal strings to the client. If you use literal and non-literal strings in the same page, make sure the code page of @CODEPAGE matches the code page of Response.CodePage, or the literal strings are encoded differently from the non-literal strings and display incorrectly.

其中比较有用的一句话是说如果Response.CodePage和@CODEPAGE不一样的话会产生乱码。也就是说当Z-blog的@CODEPAGE=65001而Z-blog的Response.CodePage被Session.CodePage赋为936的时候就会出现乱码，oblog反之亦然。

不知道上面说了这么多解释清楚没有-_-||

下面解释一下为什么SXNA有时会把Session.CodePage赋为936，我有一个版本是这样写的：

<% OriginalCodePage=Session.CodePage %>

.......

<% Session.CodePage=OriginalCodePage %>

当用户进入浏览器的时候Session.CodePage默认为936，这个时候的默认936不是程序声明的，因此不会赋给Response.CodePage，当进入SXNA的时候，Session.CodePage被上面那段代码一折腾就变成了程序声明的Session.CodePage=936,因此再进入Zblog的时候就把936给了Response.CodePage。

至此，全部原因已经分析清楚了。

因此说，保证asp叶面一定不会出现乱码的代码应该是这样的：（假定是UTF-8的叶子）

<%@ CODEPAGE=65001 %>

<% Response.CodePage=65001%>

<% Response.Charset="UTF-8" %>

进一步说明为什么要加Response.Charset，因为MSDN说应该加...呵呵

If the code page is set in a page, then Response.Charset should also be set.

另外，文件的编码格式应该与@CODEPAGE一样:

The file format of a Web page must be the same as the @CODEPAGE used in the page.

这就是为什么zblog,pjblog等一些程序要吧文件存成UTF8编码格式的原因.

综上，如果所有的程序都声明了Response.CodePage就不会被Session.CodePage干扰而出现乱码了。所以Session.CodePage还是不能轻易用的！