经典ASP（VBScript）多语言显示编码异常问题求助

Let’s break down why your Spanish (and other non-English/Chinese) text is showing up as � and how to fix it without maintaining separate files for each language—this is totally solvable with consistent UTF-8 setup.

The Root of the Problem #

Classic ASP is finicky with UTF-8, especially when it comes to file encoding order and BOM (Byte Order Mark) characters. Your current setup works for English/Chinese, but fails for other languages because:

• You might be mixing file encodings (like UTF-8 with BOM or ANSI) which conflicts with your Response.CodePage=65001 setting.
• Language files might be loaded before you set the UTF-8 response headers, so variable values are stored using the wrong encoding.

Step-by-Step Solution #

1. Standardize All ASP Files to UTF-8 Without BOM

This is the most critical step. Here’s how:

• Open Notepad++, go to Encoding > UTF-8 (not "UTF-8-BOM").
• Re-save your main ASP pages and language files in this encoding.
• Why no BOM? The BOM characters () get sent as the first output to the browser, which breaks the UTF-8 parsing and overrides your Response.CharSet settings. ANSI only supports one code page (e.g., GB2312 for Chinese, ISO-8859-1 for Spanish) so it can never support multiple languages at once.

2. Load Language Files After Setting UTF-8 Headers

Your response encoding settings need to be active before the language file assigns variable values. If you load the language file first, the variables will be stored using the default server encoding, not UTF-8.

Correct Page Structure (index.asp):

<%@LANGUAGE="VBSCRIPT" CODEPAGE="65001"%>
<% 
Option Explicit
' Set UTF-8 encoding FIRST
Response.CodePage = 65001 
Response.CharSet = "utf-8" 
Response.CacheControl = "no-cache" 
Response.AddHeader "Pragma", "no-cache" 
%>
' Now load the language file
<!--#include file="lang.asp"-->
<!DOCTYPE html>
<html>
<head>
    <meta charset="UTF-8"> <!-- Match the response charset here too -->
    <title><%=page_title%></title>
</head>
<body>
    <p>Today is <%=day_name%></p>
</body>
</html>

3. Clean Up Your Language File

Make sure your language file only handles variable assignments—no stray output (even blank lines or spaces outside <% %> tags!). Any unintended output will trigger the response headers to send early, making your encoding settings useless.

Example lang.asp (saved as UTF-8 without BOM):

<%
Dim language, day_name, page_title
' Get language from your preferred source (Cookie, URL, request header)
language = Request.Cookies("user_language") ' Or Request.QueryString("lang")

If language = "Spanish" Then
    day_name = "lunes"
    page_title = "Página de inicio"
ElseIf language = "Chinese" Then
    day_name = "星期一"
    page_title = "首页"
Else
    day_name = "Monday"
    page_title = "Home Page"
End If
%>

4. Test with a Clean Browser Cache

Old cached responses might still show garbled text. Clear your browser cache or use incognito mode to test the changes.

Additional Checks #

• Ensure your server’s ASP settings don’t override your encoding. The Response.CodePage=65001 should take precedence, but double-check that there’s no server-wide code page forcing.
• When pasting non-ASCII text into your language file, make sure it’s copied from a UTF-8 source (e.g., a UTF-8 encoded text editor) to avoid hidden encoding issues.

With these changes, your single language file will support all UTF-8-compatible languages—no need for separate files per language!

内容的提问来源于stack exchange，提问作者user5326446