Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 22947 invoked by uid 500); 3 Mar 2003 22:00:27 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 22934 invoked from network); 3 Mar 2003 22:00:26 -0000 Received: from anchor-post-33.mail.demon.net (194.217.242.91) by daedalus.apache.org with SMTP; 3 Mar 2003 22:00:26 -0000 Received: from media.demon.co.uk ([80.177.14.141]) by anchor-post-33.mail.demon.net with esmtp (Exim 3.35 #1) id 18pxz5-000BLm-0X for cocoon-dev@xml.apache.org; Mon, 03 Mar 2003 22:00:31 +0000 Date: Mon, 3 Mar 2003 22:00:26 +0000 Subject: Re: form encoding problems Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: Jeremy Quinn To: cocoon-dev@xml.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: <1046727579.1424.11.camel@defiant.dff.local> Message-Id: <8A2A325E-4DC3-11D7-90DA-0003935AD2EE@media.demon.co.uk> X-Mailer: Apple Mail (2.551) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Monday, March 3, 2003, at 09:39 PM, Torsten Curdt wrote: >>> I recall a similiar problem a long time ago. I solved it by changing >>> some of the HTML serializer settings. The form encoding was fine in >>> IE >>> but crap in NS/Mozilla. Sorry, cannot really remember what is was :-/ >> >> Have a beer, maybe you will remember ;) > > *hick* ...I know now ;-) > > ...well ok - I looked it up. We have set the serializer encoding to > ISO-8859-1 and it worked. At least for german :) I have got it. This was answered on the users list a while back, sorry guys. Answer, use the SetCharacterEncodingAction in the Pipeline. Works with InputModules too. Thanks for your help regards Jeremy