Sven Van Caekenberghe
sven at stfx.eu
Mon Oct 21 15:26:12 EDT 2013
On 21 Oct 2013, at 21:09, "phil at highoctane.be" <phil at highoctane.be> wrote:
> Well, for one, removing leadingChar will make the urlEncode/urlDecode work properly for the test, as now, the leadingChar thing prevents it.
Read my last comment in https://pharo.fogbugz.com/f/cases/6368/deprecate-unescapePercents-and-encodeForHTTP
I rewrote the test without the language environment stuff, it should pass.
> As it is now, leadingChar generates a code point outside of the unicode range, making leadingChar a non supportable element.
> Let's get that out.
Yes, longer term I think we should indeed remove it.
More information about the Pharo-dev