[TYPO3-core] RFC: Bug 1030, 277, 1472 possibly 1270

[Kasper Skårhøj]

I'm ok with your change.

Background for JScharCode is that the transfer of special chars to the context 
menus could only be done if all chars were converted to their Unicode value 
like that. Very weird. I didn't know if this is now obsolete or if there are 
other ways. I'm just saying that it was the only universal way I could find 
at the moment.

If there is a better way today lets implement that and make sure it is used 
EVERYWHERE JS labels are used so it works for every charset (also non-UTF8 of 
course!). I'm OK with the change if you are committed to fix any problems it 
might have. And you can author some thing for the coding guidelines .

- kasper


On Saturday 17 December 2005 14:09, Bernhard Kraft wrote:
> Bernhard Kraft wrote:
> > Branches:
> > Head, 3.8
> >
> > BT reference:
> > http://bugs.typo3.org/view.php?id=277
> > http://bugs.typo3.org/view.php?id=1030
> > http://bugs.typo3.org/view.php?id=1472
> > possibly:
> > http://bugs.typo3.org/view.php?id=1270
> >
> > Description:
> > The good old unescape(rawurlencode(...)) problem :)
>
> Any further comments on this ?
>
> Would like to get it in 4.0.0 which is to be release soon ...
>
> This is really a bad gremlin which itches a lot if you make utf-8 sites -
> which is in my opinion the only choice if you are a non-Japanese Editor
> having an English or German Backend and just copy and pasting exactly
> translated texts.
>
>
> greets,
> Bernhard

-- 
- kasper

-----------------
"A 'please' would be nice", John Travolta, Pulp Fiction