Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 64774 invoked from network); 26 Jun 2004 14:27:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 26 Jun 2004 14:27:24 -0000 Received: (qmail 16443 invoked by uid 500); 26 Jun 2004 14:27:13 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 16301 invoked by uid 500); 26 Jun 2004 14:27:10 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 16206 invoked by uid 99); 26 Jun 2004 14:27:07 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.27.1) with SMTP; Sat, 26 Jun 2004 07:27:06 -0700 Received: (qmail 9569 invoked by uid 65534); 26 Jun 2004 14:27:00 -0000 Received: from a183069.studnetz.uni-leipzig.de (EHLO [139.18.183.69]) (139.18.183.69) by mail.gmx.net (mp026) with SMTP; 26 Jun 2004 16:27:00 +0200 X-Authenticated: #3483660 Message-ID: <40DD87C2.2010406@gmx.de> Date: Sat, 26 Jun 2004 16:27:14 +0200 From: Joerg Heinicke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: de-de, de, en-us, en-gb, en MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: UTF-8 and Encoding Problems References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On 23.06.2004 23:44, Christopher Painter-Wakefield wrote: > Are you using Tomcat? If you do some searches, you'll probably turn up > other postings on this topic. I can't remember all the ins & outs, but > supposedly the browsers incorrectly supply encoding information in their > requests to Tomcat (ours were POST requests), and Tomcat by default assumes > ISO-8859-1 encoding for the submitted form data. This gives you garbage > data for anything outside plain ASCII, if your browser sends it in UTF-8. > I found some webapp filter class that works with Tomcat to coerce the > character encoding (or Tomcat's perception of the encoding) for all > requests to UTF-8, to match all of our pages and forms. I can send you our > filter and the web.xml entries separately; if you want them, just e-mail > me. There may be better solutions now with Tomcat 5, but we have just kept > on using this old filter, and it seems to do the trick. > > (Now that I think about it, I think this filter is/was supplied with the > Tomcat source distribution, maybe. Look for the SetCharacterEncodingFilter > class.) Wouldn't setting 'form-encoding' to UTF-8 do the same? Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org