Well, for one, removing leadingChar will make the urlEncode/urlDecode work properly for the test, as now, the leadingChar thing prevents it.
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. Phil
