Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3E639C07.8030900@dff.st>
Date: Mon, 03 Mar 2003 19:16:39 +0100
From: Torsten Curdt <tcurdt@dff.st>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3a) Gecko/20021212
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: form encoding problems
References: <BA15ED53-4DA2-11D7-90DA-0003935AD2EE@media.demon.co.uk>
In-Reply-To: <BA15ED53-4DA2-11D7-90DA-0003935AD2EE@media.demon.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

> Hi All,
> 
> This is possibly a trivial mistake ... but I never came across it before.

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 :-/

> I have a search form for searching Lucene. Mozilla confirms the page is 
> in UTF-8 encoding.
> 
> I enter a string with accented characters into the query field. eg 
> '�clair' (e-acute).
> 
> The form comes back with the string now reading 'éclair'. (A-tilde, 
> Copyright sign). Mozilla says the encoding is still UTF-8. (The value 
> has been picked up by an InputModule and fed via the SiteMap to XSLT).
> 
> The query string in the URL reads 'query=%C3%A9clair', which are the 
> unicodes for 'A-tilde' and 'Copyright' characters. (Which would imply to 
> me that the Browser incorrectly encoded the query.)

How do other browsers behave?

> This makes me feel like I have done something really dumb, but I cannot 
> work out what ;)

Well, good luck :)

> Any suggestions?

Have a beer and then come back - maybe you'll see it then ;)

cheers
--
Torsten