Previous versions of CMT tried to preserve files character encoding for files that were created outside of CMT. This could cause save/overwriting issue when trying to save characters that were not supported by the file original encoding scheme. Because this error occurred during the writing process, in the worst case it could cause the content of the file to be wiped (but if you didn't disabled CMT backup systems then there would still be two backups made before trying to actually overwrite the file, so nothing was really lost).
To prevent these issues, I added two options (activated by default) : "Safe file write" and "Change file encoding on write error".
The first option ("Safe file write") when enabled, adds an intermediate step in every save process : the file to be saved/overwritten is copied, then the changes are saved in the file's copy and not in the original. If no error occurred during the save process using the copy, then and only then we replace the original file with the copy, and delete the copy. This intermediate step is transparent from the user perspective, nothing changes.
The second option defines what happen when an error occurs during the "safe file write" step explained above.
When "Change file encoding on write error" is disabled, then the user will just be warned that the file couldn't be saved, and he will have the error crash to report. The original file will stay as it was, the changes won't be saved.
When "Change file encoding on write error" is enabled (default), then CMT will first try to save the file using a different encoding, starting with UTF-8. If this still fails, then the user will just be warned that the file couldn't be saved, and he will have the error crash to report.
So, if you absolutely want to keep your files encoding scheme, disable "Change file encoding on write error". If you don't mind, then keep it enabled. Again, this change of encoding will only occur when required, which for most users is never or very very rarely. If you never had this error before in CMT, it means this error never happened to you, so it probably won't happen at all.
@bWWd
