cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reinhard Poetz" <>
Subject RE: [heads up] cocoon's defaults form-encoding and seerialize-encoding are inconsistent.
Date Mon, 03 Nov 2003 10:01:52 GMT

From: Marc Portier


> So as a recap:
> Given the fact that todays browser behaviour is coupling
> 1. the encoding of the HTML-stream (from server to browser) 
> describing 
> the <form>
> to
> 2. the encoding used to encode the request params in the HTTP-request 
> hosting the form-submit (from browser to server),
> the web-app-developer is kind of forced into doing a decent effort in 
> making sure on the server-side he is decoding the request-params with 
> the same encoding as was used to serialize the HTML with.
> The above observation made me label our current default-settings for 
> both encodings inside Cocoon to be 'inconsistent':
> - if you don't specify an encoding for the serializer (sitemap.xmap) 
> it's utf-8
> - if you don't specify an encoding for the form-decoding 
> (web.xml) then 
> it is iso-8859-1
> To fix this I'ld like to:
> use the context as described above to communicate the chosen (or 
> implicit) form-decoding to the AbstractTextSerializer so it 
> can use that 
> as a natural default-encoding (currently there is no such thing as a 
> default-encoding for the AbstractTextSerializer resulting in it being 
> chosen by xalan)
> as a consequence however this would mean that the 
> default-encoding for 
> the serializers changes from utf-8 to iso-8859-1
> we could take the other path and let the fix go together with 
> changing 
> the form-decoding to utf-8
> The remaining question being: Which path do people prefer? Are there 
> clear argumentations to rule out one or the other? do we vote?
> -marc=
> PS: I do hope this clears out the confusion?

Yes, thank you Marc!

I would prefer iso-8859-1 but this is just a feeling and no opinion
based on facts ;-)


View raw message