> Is it really that lame, that you cannot specify encoding in which to > save? Any reasonable Unix editor has that option. VS editor treat files without BOM as ASCI/current encoding preferred by user. It's differs with ncc behavior. And it's cause user mistakes. UTF-8 files contain BOM and correctly open by VS.