The solution is to explicitly set the character encoding to utf-8. I do this in the aspx file's head section and it works fine.
This is kinda wierd though as with an aspx file, it seems that dotnet will always insert this charset header for you by default (you can see this by running wget in debug mode, withough setting the charset in the head section). However this does not work when using wget. It does work in normal browsers though as aspx files with utf-8 chars obvioulsy display fine. Anyway problem solved, just thought I'd let you know. -----Original Message----- From: Hrvoje Niksic [mailto:[EMAIL PROTECTED] Sent: March 31, 2005 3:19 PM To: Alan Hunter Cc: 'wget@sunsite.dk' Subject: Re: Character encoding I'm not sure what causes this problem, but I suspect it does not come from Wget doing something wrong. That Notepad opens the file correctly is indicative enough. Maybe those browsers don't understand UTF-8 (or other) encoding of Unicode when the file is opened on-disk?
