The problem appears to be that many of the characters on that page are
not actually UTF-8 and just adding the content-type header doesn't
actually make it so. The browser's are, in this case, being overly
helpful and either converting the non-UTF8 characters or otherwise
displaying them correctly. We could technically automatically convert
non-UTF8 characters, but we try not to magically modify user content.
Once that's resolved, things should work fine.
Also, if you want to test this more quickly until you get it, you can
create a campaign via the web interface and use the import from url
option on it and check the display using the pop-up preview. The code
the API uses to import from a url is exactly the same.
jesse
> OUT*&output=json&type=regular&options[list_id]=5ec83b7cfb&options[generate_text]=true&options[to_email]=Subscribers&options[subject]=Test
> no Newsletter - Thursday, July 08, 2010&options[from_name]=Intrafish
> Media&options[from_email]=
nore...@intrafish.com&content[url]=
http://www.intrafish.no/ext/mailchimp/no_html.jsp