[TYPO3-core] RFC: replacement for rawurlencode/unescape

[Martin Kutschker]

Karsten Dambekalns schrieb:
> Hi.
> 
> On 08.10.2006, at 18:26, Martin Kutschker wrote:
> 
>> So I suggest we change all PHP code that generates URL encoded to one
>> that prepares for decodeURIComponent() and vice versa. In effect this
>> means that any string prepared for JS has to be converted to UTF8  before
>> going through rawurlencode. In JS we need only to replace unescape()
>> with decodeURIComponent.
>>
>> When we receieve data from JS that has been encoded with
>> encodeURIComponent (instead of escape()) we need to convert the data
>> from UTF8 to the current charset after applying rawurldecode. This is
>> mostly the case for wizards.
> 
> Sounds like quite a bit of work. How does the necessary change look  
> like? Is this a task that is mostly tedious, or does it need a Real  
> Brain[tm] to be done?
> 
> Any estimate and/or example at hand?

No, and in reality it only matters if we pass non-ASCII data. Maybe we can 
change it onyl when we move to UTF8 data. I was thinking of a clean up, but 
given the current situation there are more important matters.

Masi