We have some log files that reliably show up as hex in Sublime Text 2 and the beta 3. Here is very truncated example (which I also tried to attach, but it was rejected):
— start file —
Reply(STATUS)
— end file —
where represents some odd character.
In ST2 and ST3 beta this shows up as:
— start excerpt —
5265 706c 7928 0053 5441 5455 5329 0a
— end excerpt —
Aside from the bizarre display, ST gives no visual indication that anything is odd about the file. Now we know it opened the file in Hex mode, but we didn’t at the time: it just looked like garbage. We wasted a lot of time tracking this down.
Is there some way to get it to always treat such files as UTF-8 by default?
Also, I please consider displaying the current encoding along the bottom of the window. That way it would be a lot clearer what’s going on. We can’t be the only people who have been thrown by this.