Hi,

I tested a GB2312-based JSP page on Tomcat 4.1.12, and it worked fine.
(The attached file).
It shows ni-hao-ma in simplified Chinese character system and the
response encoding, i.e. GB2312. The key point I'd like to make clear is
that encoding of a JSP page should keep up with that of response that
the page generates for the best delivery of content, in particular,
under non-latin-1 character sets.
This concept is actually introduced to JSP 2.0 spec explicitly with JSP
configuration feature. I believe localization issues will be smoothly
gone with Tomcat 5 and other containers compliant with JSP 2 style.
P.S. a tech-tip for page encoding: Dreamweaver helps adjust page
encoding to a specific character set, such as EUC-KR, and certainly
GB2312. (I did this with Dreamweaver MX although I use Windows XP Korean
version.)

-----Original Message-----
From: Steve Chai [mailto:[EMAIL PROTECTED]] 
Sent: Friday, September 27, 2002 2:11 AM
To: [EMAIL PROTECTED]
Subject: Question about Internationalization

Hi,

I am using Tomcat 4.1 now. I got the internationalization problem.
In my jsps, the charset is set to gb2312, which is for chinese, but the 
chinese character can not show up correctly.

These jsps are running very well in Tomcat 4.0.4. However after I did
the 
following replacement, they are also running well in Tomcat 4.1.

What I did is:

In Tomcat 4.1\common\lib folder, just simply replace jasper-compiler.jar

jasper-runtime.jar and servlet.jar with Tomcat 4.0.4 version's. Then it 
works well.

Is it a bug ? or I have to config something in Tomcat 4.1 for 
Internationalization.

Please give me feedback.

Thanks

Steve Cai





_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

Attachment: test.jsp
Description: Binary data

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to