[TYPO3-core] Re: Re: Re: FYI72: #15130: Backend search does not find non–latin1 characters

[Steffen Kamper]

Hi,

Dmitry Dulepov schrieb:
> Hi!
> 
> Martin Kutschker wrote:
>> I hope that just removing the call is enough. But as I have written repeatedly: rawurlencode() is
>> NOT to be used on non-ASCII data. Anyway, you will need it or its's "newer" cousin decodeUrl only
>> when dealing with URLs (and GET data). Don't use it for POST or JS strings.
> 
> Removing that call solves the problem, so I also think it is enough.
> 
>> Note to the clean up team: remove all the unnecessary calls to rawurlencode in the BE and get rid of
>> the JS string (de-)composition with charCodeAt().
> 
> There are also lots of escape/unescape calls in JS. They should be replaced
> with encodeURIComponent/decodeURIComponent (or encodeURI/decodeURI for path
> segments and full URIs).
> 

this can change with the project "UTF-8 in BE" so we also lose the 
puzzle with latin chars in JS.

vg Steffen