[TYPO3-core] RFC: #3527: Bug: Wrongly encoded characters in mail form validation popup
Francois Suter
fsuter at cobweb.ch
Fri Mar 27 15:28:52 CET 2009
Hi,
> -1 as this cannot work correctly unless the character set is utf8 as
> decodeURI() expects utf8 while unescape() expects latin1. If you use
> decodeURI() you must convert the data to utf8 on the server side before
> using rawurlencode().
>
> But... I think we don't need any escaping for strings *within* JS. The
> escaping is only needed when passing values via URLs.
Hmm, indeed I apparently misunderstood your explanations. I tried to
just remove the unescape() call, but it's worse than before. Do you mean
the proper solution is to remove both the unescape() calls in the JS
*and* the rawurlencode() calls in tslib_content?
Cheers
--
Francois Suter
Cobweb Development Sarl - http://www.cobweb.ch
More information about the TYPO3-team-core
mailing list