Re: Non-Latin Character Display

2007-03-17 Thread Rashmi Rubdi
rset/index.html I'm not sure if the above will be of use to you. Also some additional related links: http://www.w3.org/International/O-charset.en.php -Rashmi - Original Message From: Vernon _ <[EMAIL PROTECTED]> To: users@tomcat.apache.org Sent: Saturday, March 17, 2007 1:13:23

Re: Non-Latin Character Display

2007-03-17 Thread Vernon _
> As I mentioned in my post, I already have the JSP page set as> > HTML: /> > JSP: <%@ page contentType="text/html;charset=UTF-8" language="java" %> Mark was suggesting that you set the request encoding, not the response encoding. The above is character set setting which is different from

Re: Non-Latin Character Display

2007-03-16 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vernon, Vernon _ wrote: > As I mentioned in my post, I already have the JSP page set as > > HTML: > JSP: <%@ page contentType="text/html;charset=UTF-8" language="java" %> Mark was suggesting that you set the request encoding, not the response encod

Re: Non-Latin Character Display

2007-03-16 Thread Vernon _
able to resolve. I have to move long text into a message property file to go around this problem. Original Message Follows From: Mark Thomas <[EMAIL PROTECTED]> Reply-To: "Tomcat Users List" To: Tomcat Users List Subject: Re: Non-Latin Character Display Date: Fri, 16 Mar

Re: Non-Latin Character Display

2007-03-16 Thread Mark Thomas
Vernon _ wrote: > I believe that is a TC configuration related issue. After having "set > JAVA_OPTS= -Dfile.encoding=UTF-8" There is no need to do this. This setting is read only on some JVMs. Try the following. If you use GET, you'll need to set the encoding in the connector as well. <%@ page co