On Mon, 3 Dec 2001, Ing. Gabriel Gajdos wrote:
Date: Mon, 3 Dec 2001 09:41:39 +0100
From: Ing. Gabriel Gajdos [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE2: Jsp compile option for Big5 encoding / encoding question
Craig (or somebody
Message -
From: Ing. Gabriel Gajdos [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, December 04, 2001 4:02 PM
Subject: RE: RE2: Jsp compile option for Big5 encoding / encoding question
Thanx Craig, but I affraid, this was not the problem.
|
| JSP (start file):
| %
|String
Thanx Craig, but I affraid, this was not the problem.
|
| JSP (start file):
| %
|String contentType = text/html;charset=windows-1250;
|response.setContentType(contentType);
| %
|
|
| The setting windows-1250 is not a valid character encoding name in Java.
| Try Big5 instead for
Craig (or somebody else), could you, please, give me a hint in following question?
| JSP pages follow these rules:
|
| * If you declare a pageEncoding attribute on your %@ page %
| directive (supported in JSP 1.2 only), that character set is used
| to read the text of the page itself (as
Thanx, Craig, but something is wrong...
| Yes, dynamically setting the content type and character encoding is
| supported in JSP 1.2 (and therefore in Tomcat 4). You have three choices:
|
| * You can use a scriptlet to set the content type at the top of your
| JSP page:
|
| %
| String
On Mon, 3 Dec 2001, Ing. Gabriel Gajdos wrote:
Date: Mon, 3 Dec 2001 11:02:50 +0100
From: Ing. Gabriel Gajdos [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: RE2: Jsp compile option for Big5 encoding / encoding question
Thanx, Craig
