Peter Van Hove wrote:
>> While writing this, I think I introduced a bug in function
>> UrlEncode which always converted to UTF-8 in V7.
>> I just checked in a change, both UrlEncode and UrlDecode take a
>> CodePage argument now.
>
>>
>> Yes now there is ;-), update your local work copy and use Ur
> I tried to update but no files were changed.
> Still "Completed: At revision: 297"
> Did you really check in ?
The SVN HTTP version does seem to be showing revision 297 which is 10
days old, I'll see if the server has stopped or something.
You should really be using proper SVN or TortoiseSVN, w
>> Should I URL encode the POST data as well ?
>
> Yes.
I did ... it did not help.
I used your older URLEncode() function that has UTF-8 conversion hard coded
in it (I could not check out the newer version, see other email).
I came to the conclusion that the '=' sign cannot be encoded as then it
> While writing this, I think I introduced a bug in function
> UrlEncode which always converted to UTF-8 in V7.
> I just checked in a change, both UrlEncode and UrlDecode take a
> CodePage argument now.
>
> Yes now there is ;-), update your local work copy and use UrlEncode()
> located in uni
Peter Van Hove wrote:
>>> Interesting !!!
>>> So POST and GET data, when sent to a host, are not unicode ?
>>
>> They are not sent as UTF-16 Unicode, correct.
>>
>>> And so what I provide to the component when I do a GET, in unicode,
>>> is converted in the component to something else (UTF 8 ?)
>
