Sublime Forum

Bug: Non-UTF8 characters broken on ST3 start (detailed)

#1

Description:
When ST3 is restarted, if the project is in non-utf8 encoding, all files need to be reopened, otherwise they are unreadable.
I have attached 2 screenshots to show:

  1. File in ST3 before ST3 is closed - *(http://i.imgur.com/dYvRFoF.png)
  2. File right after ST3 is started again - *(http://i.imgur.com/ennd5s3.png)

Environment:
ST3 (windows 7 ultimate x64, st3 build 3083).

How to reproduce:

  1. Create a project with settings:

"default_encoding": "Cyrillic (Windows 1251)", "fallback_encoding": "Cyrillic (Windows 1251)"
2. Create some files, write some russian text in that files.
3. Close ST3.
4. Open ST3.

Observed behaviour:
All russian text in files which have been open is now broken. I need to manually close the files and open them again too see the normal russian text.

Expected behaviour:
When ST3 is restarted, I expected to see readable text in the files that have been open right before ST3 was closed.**

0 Likes
#2

Probably it’s not only UTF-8 problem, I have same issue with windows-1250 switching to windows-1252.

0 Likes
#3

I think this issue was already reported, the problem is when the encoding is defined in the project.
If I remember well, the encoding of the project is not used when the files that was already opened is reopened,the files you open later or the new created files are OK.
I suppose the issue is that the encoding of the project is read too late.

0 Likes
#4

I posted this into the Issue Tracker: github.com/SublimeTextIssues/Core/issues/815

0 Likes