[Seaside-dev] Seaside 3.0a6ish

[Paolo Bonzini]

On 05/20/2010 11:12 AM, Philippe Marschall wrote:
> There's one trouble point:
> WAUrlEncoder>>  #nextPutAll:
>
> The trouble is we first need to convert a URL to bytes and then
> interpret these bytes as Latin-1 and do percent encoding accordingly.

Really?  Shouldn't the percent-encoded strings use whatever encoding the 
page uses?  Surely, browsers use whatever encoding the page sent when 
creating their responses.

Alternatively, _do we need to use percent encoding at all_?  Including 
HTML-encoded Unicode characters in <a> tags, like

   <a href="http://www.google.com/search?q=&#176;">test</a>

or

   <a href="http://www.google.com/search?q=&#32176;">test</a>'

should just work.

Paolo