RE: Problem with UTF encoding with Action Form

2002-02-07 Thread Chris Birch
Hi, The following is taken from javax.servlet.ServletResponse: --- The charset for the MIME body response can be specified with setContentType(java.lang.String). For example, "text/html; charset=Shift_JIS". The charset can alternately be set using setLocale(java.util.Locale). If no charset is

Re: Problem with UTF encoding with Action Form

2002-02-07 Thread Antony Stace
Hi Chris Thanks for the reply. On Thu, 7 Feb 2002 12:32:27 - "Chris Birch" [EMAIL PROTECTED] wrote: Hi, The following is taken from javax.servlet.ServletResponse: --- The charset for the MIME body response can be specified with setContentType(java.lang.String). For example,

RE: Problem with UTF encoding with Action Form

2002-02-07 Thread Chris Birch
fully that should do the trick. Regards, Chris. -Original Message- From: Antony Stace [mailto:[EMAIL PROTECTED]] Sent: 07 February 2002 13:11 To: Struts Users Mailing List Subject: Re: Problem with UTF encoding with Action Form Hi Chris Thanks for the reply. On Thu, 7 Feb 2002 12:32:27 -

Re: Problem with UTF encoding with Action Form

2002-02-07 Thread Antony Stace
Thanks Chris for the reply. I've just looked in the JSP spec. and you're quite right, the "@page content ..." directive sets the encoding used by the Writer. You also correctly stated that you need: meta http-equiv="Content-Type" content="text/html; charset=UTF-8" as well. Hopefully

RE: Problem with UTF encoding with Action Form

2002-02-07 Thread Chris Birch
... Regards, Chris. -Original Message- From: Antony Stace [mailto:[EMAIL PROTECTED]] Sent: 07 February 2002 13:47 To: Struts Users Mailing List Subject: Re: Problem with UTF encoding with Action Form Thanks Chris for the reply. I've just looked in the JSP spec. and you're quite right, the "

Re: Problem with UTF encoding with Action Form

2002-02-07 Thread Michael Baldwin
Try reading a really good resource on character set encoding. http://tagunov.newmail.ru/i18n/i18n.html It sounds to me like the request params aren't being decoded properly when they are being processed by the web container. I'd suggest looking at the section on Decoding request parameters