JSPs that use a character set other than the server default require additional changes in source code and deployment properties.
In your JSP source code, specify the encoding in the page declaration, for example:
<%@ page contentType="text/html;charset=BIG5" %>
When initializing strings, pass the encoding name to the String constructor, for example:
byte[] b = { (byte)'\u00A4', (byte)'\u00A4',
(byte)'\u00A4', (byte)'\u00E5' };
String s = new String(b, "big5");
If you do not specify the encoding name, the byte array may be converted incorrectly.
When deploying localized JSPs, group JSPs for each language in their own directory tree under your Web application’s context root. For example, all files under /en are English, 8859_1 encoded, and all files under /ko are Korean, KSC5601 encoded.
