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

[Karsten Dambekalns]

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?

Regards,
Karsten
-- 
Karsten Dambekalns
Gimme Five!
http://typo3.org/gimmefive


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 304 bytes
Desc: This is a digitally signed message part
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20061030/1eb4737c/attachment.pgp