>>but I suspect it does not come from Wget doing something wrong. I'm not so sure about that, it displays different output for the same infile, when only the extension of the infile changes. I tried with the exact same file spidered three times, only changing the extension between each spider.
infile = 69 bytes .html outfile = 69 bytes .zzz outfile = 69 bytes .aspx outfile = 66 bytes So either it is wget or something screwy with asp.net. As I said, i don't know the inner workings of either so i'm not sure. I'll try to set up the example on a public svr in the next few days. -----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?
