I am currently using Sublime Text 3 for coding, and while most works as desired, I have seen one major draw back from Sublime Text 2. When opening a file, in an odd character set (at work we use IBM-858, yes it is suboptimal). When opening a file in this characterset, and simply saving it, special characters are corrupted, even though no content was changed. See screenshot below:
When doing the same thing in Sublime Text 2, the content is the same as before the save, which is what one would expect. Both report the file as being in the format Windows-1252, which I guess is what comes closest to IBM-858. It works in Sublime Text 2, but not in Sublime Text 3. Fallback encoding in both versions is the same:
"fallback_encoding": "Western (Windows 1252)",
Is there a solution to this, or is this a bug?