I saw that I posted a similar thread back in 2009 (http://forums.adobe.com/thread/531099).
And this is still a big leak in Dreamweaver if you ask me. I'm now sitting on PC, and I experience the exact same bug/horrible default option.
Its beyond me that this hasn't been fixed now even in the latest DW version. I don't know how many hours of unnecessary debugging this have cost me.
Still, if I create a new file using DW, the file encoding will be ANSI on a PC, and I will have to open it up in notepad, resave it as UTF-8, open it up again in DW, go into the above configuration and uncheck "Include Unicode Signature (BOM)".
I'd very much appreciate if you can explain how to avoid this detour just to create new files - cause I still enjoy this editor very much, else I wouldn't buy it. But it really is starting to get on my nerves now.
And please explain to me why the "Include Unicode Signature (BOM)" is checked by default? I see so many frustrated DW users out there who think that their code is wrong somewhere, when its actually DW because this BOM "feature" is counted as an output in PHP.
I assume you have this memorized, but just in case