|Think about Loose Coupling|
Re: can't get rid of BOM from UTF-8 webpageby Anonymous Monk
|on May 20, 2012 at 08:15 UTC||Need Help??|
My second question is why Perl insists on keeping the BOM and printing it later
Because it would be insane to throw it away without being told to throw it away.
I would have expected it to be stripped during the initial read of the text file, since it's just packaging, and omitted in Perl's internal character representation.
Besides not being mere packaging it isn't "omitted"; Your expectations is wrong.
Overall, though, I'd like to learn where to fix the problem. Do I configure Windows differently? Do I read the text file differently in Perl? Or do I just print things differently in Perl? Any insights or suggestions will be greatly appreciated.
for cmd.exe change fonts, I read fonts are responsible for not showing BOM
or try PowerShell, I hear that thing is unicode by default, so it ought to come with fonts that know to hide BOM
or from perl, strip the bom , say by using :encoding(UTF-8):via(File::BOM), and/or skip printing BOM when -t Filehandle is opened to a tty (tty means console, cmd.exe )
I've seen lots of suggestions ...
Next time, include those links in your post :)
FWIW, Content-type is not charset
BUT, FWIW, you shouldn't specify charset (utf8 or UTF-8) to decoded_content, that is webservers job , it should just work already
My first question is why the CMD prompt isn't handling the BOM correctly,
seems to me something on MSDN would answer that :p