TYPO3 Core

JS escape() and unescape() are not fit for UTF8. In the old days they used to be character set ignorant (ie all bytes were escaped as-is), but nowadays a the data is converted from or to latin1 (iso-8859-1) before being escaped.

The safe way in modern browsers is to use encodeURIcomponent/decodeURIcomponent which operates on UTF8 data.

After i had replaced "unescape" with "decodeURIcomponent" in the file jsfunc.validateform.js the problem is solved (on my suse linux 10.1 system) while using the browser mozilla firefox or seamonkey. When using the browser Konqueror then the problem is not solved. other browser like ie i will test tomorrow.

I think the Problem is solved.

Important: It's not "decodeURIcomponent" but "decodeURIComponent" (upper-case "C"), otherwise it will fail at least on Firefox 3.

Attached is a patch that seems to solve the problem. However I would like Martin to give a feedback about it, as he is more familar with the topic.

How to reproduce/test:
1. Create a form that has form fields containing umlauts
2. Make the field required and don't fill it in

- michael

Masi, can you please take a look at this solution?
Thanks in advance!
- michael

i can confirm that using decodeURIComponent solves the problem.

I think all "unescape" calls in core should be replaced by "decodeURIComponent" ("escape" as well)

Steffen, that is not the way I want this to be solved.
As far as I know, "decodeURIComponent" is not a successor of the "unescape" function, but provides a different way of encoding data which probably seems to work in this case. However, it may also introduce new problems at many places.

That's why I asked Masi for some feedback as he seems to be more familar with it already...

Michael, look to #19502 where we solved it same way, Masi was involved too (see corelist)