[TYPO3-core] Bugfix #2396

[Kasper Skårhøj]

How does the local sl() function look? If I wrap that function it is  
usually because it is used in both frontend and backend, but if you  
can't see that from the local sl() implementation I guess it  
doesn'tmake sense. yet it could spoil backwards compability if  
someone extends that class.

- kasper

"A contribution a day keeps the fork away"
-------------------------------
kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej |  
gizmo: kasper_typo3


On Jan 31, 2006, at 18:31 , Bernhard Kraft wrote:

> Holzinger Franz wrote:
>> Hello Bernhard,
>>
>>
>> what has been the reason for this change:
>>
>>
>>> -							$dataAcc[$eKey]=rawurlencode($pvpv[1]).'|'.rawurlencode 
>>> ($pvpv[0]);
>>> +							$dataAcc[$eKey]=rawurlencode($pvpv[1]).'|'.rawurlencode 
>>> ($this->sL($pvpv[0]));
>>>
>>
>> Please explain.
>
> There is a local wrapper for $LANG->sL in t3lib_transferdata ... it  
> is used in all other places except
> this one ... it seems cleaner to use the wrapper everywhere ... if  
> you ask yourself why there is a local
> wrapper for sL in this class i must just say: I don't know.  
> Pherhaps Kasper wanted to make it possible to
> let this local sL behave differently than the $LANG one.
>
>
> greets,
> Bernhard
> _______________________________________________
> TYPO3-team-core mailing list
> TYPO3-team-core at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-core