[TYPO3-core] RFC: #3527: Bug: Wrongly encoded characters in mail form validation popup

[Francois Suter]

REMINDER #2

Especially for Masi ;-) Could you check my second version of the patch 
and see if I understood your explanations right?

> REMINDER #1
> 
>> Hi,
>>
>>> Yes, but ONLY if tslib_content does something like that:#
>>>
>>> $content = <<<EOT
>>> <script>
>>> var dummy = '$foobar';
>>> </script>
>>> EOT;
>>>
>>> Ie. it creates a JS string embedded in the HTML code. In this case the
>>> browser should handle the charset all by itself.
>>
>> That's the case. The "onSubmit" call is prepared by tslib_content and 
>> added to the HTML of the FORM.
>>
>>> Really old browser that require unescape() to handle latin1 will choke
>>> on utf8 no matter what you do :)
>>
>> Yes, but I think it's reasonable to forget about those.
>>
>> So here's new patch removing calls to rawurlencode() in tslib_content 
>> and all calls to unescape() in the validateForm JS.
>>
>> Hoping I'm on the right track this time.
> 

Cheers

-- 

Francois Suter
Cobweb Development Sarl - http://www.cobweb.ch