Hi Sharpy,
I suspect using similar techniques to the prevention of sql injection as so on
would be needed here.
i.e., the string should be encoded / deencoded before being passed to or read
from localizedValueForKey.
cheers,
Lachlan
> On 16 Feb 2016, at 9:16 PM, getsh...@gmail.com wrote:
>
>
Hello list,
I’ve been using ERXLocalizedString for render time localisation support.
It recently fell over when an EO attribute value was bound starting with the
character '@'.
The KVC support in ERXLocalizer.localizedValueForKey identifies my String as
containing the _localizerMethodIndicator
