It would be good if Sublime Text took note of the byte order mark (BOM) of unicode documents. This issue came up for me when viewing the output of a Powershell script.
A demonstration of the issue:
1. In Powershell, type this in:
"hi there" | out-file hi.txt
2. Open hi.txt in Notepad. No problem.
3. Open hi.txt in Sublime Text. Gibberish.
4. Open hi.txt in a hex editor. Note the BOM (FF EE) at the beginning.