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 under Servlet 2.3 containers". The 2.3 method on the request, "request.setCharacterEncoding( String env )". It might be just what you're looking for. As long as you call this method before any of there request params are read (which means you'll have to mod the controller servlet), you can specify whatever encoding you want when reading the chars from the request. You could get fancier with supporting multiple character sets in your app by checking the user's locale and making some assumptions about what character sets are used (GB for Chinese, Big5 for others, etc.) --Michael Antony Stace wrote: > 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 that should do the trick. > > Umm.....I have this and I get the garbage characters....Where to go from here I >wonder. > > -- > > Cheers > > Tony。 > --------------------------------------------------------------------- > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
