[Typo3-dev] Charset Bug ?

[Martin Kutschker]

"Kasper Skårhøj" <kasper2005 at typo3.com> schrieb im Newsbeitrag 
news:mailman.652.1111509596.22129.typo3-dev at lists.netfielders.de...
> Hi Bernhard,
>
> It will be wrong to substitute rawurlencode with addslashes since
> "unescape" is the javascript opposite to rawurlencode. So they are
> incompatible.

escape is NOT compatible with rawurlencode as I have already reported. They 
used to be, but are not since IE 5.5 and Mozilla 1.3 (because of 
ECMA-script).

For BE I suggest to replace *all* JS-escapes with de/en-codeURIComponent. IE 
5.5 has problems with the BE anyway (because of getElementById) and Mozilla 
1.0 is old anyway.

> Maybe your solution works for you but I fear it will not work for
> others. I had to convert chars to a series of UNICODE values for getting
> this to work in the backend for localization so it is most like much
> more complex to solve the problem generally.

It's a problem for FE because you need browser sniffing. No real problem for 
BE.

Masi