LWP output encoding

[Andy Armstrong]

On 23 Nov 2005, at 15:43, Matt Lawrence wrote:
> That still doesn't explain why the Arabic one succeeded, I get that
> error on any string containing characters over 255. The source of
> HTTP::Message shows Encode::decode being used to generate the return
> value, so arabic should really cause it. *shrug*

I'm prepared to leave that as an unsolved mystery. I suppose my main  
concern is 'does $res->decoded_content /always/ correctly return  
unicode' - and the arabic text thing was what raised doubts.

-- 
Andy Armstrong, hexten.net