lucy24 - 10:12 pm on Feb 17, 2012 (gmt 0)
If you do it that way, what happens to the encoding? The root problem is that OP's site uses UTF-8-- which is perfectly appropriate-- while the destination site uses, of all things, 8859-15, aka Latin-9.
All characters are encoded before sent (spaces are converted to "+" symbols, and special characters are converted to ASCII HEX values)
but this doesn't really give the necessary information.
More ominous is the list here:
Note that it includes the full series of %8\h and %9\h -- and those shouldn't even exist. They're Windows-Latin-1 encodings that aren't recognized by unicode, though they may de facto work on sites headed 8859-1 (not -15).