-
Notifications
You must be signed in to change notification settings - Fork 780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File is corrupted while saving differences in changed file (Ctrl+S) #607
Comments
File is corrupted the same on 2.16.9-x64 and 2.16.10-x64 versions. |
Could you show me a file that can reproduce the bug? |
Remove .txt and you got the original. |
Thank you for attaching the file. WinMerge uses mlang.dll by default to attempt automatic detection of file encoding. mlang.dll seems to think that the file encoding of the file is UTF-7 (codepage = 65000). Saving the file as UTF-7 will replace the characters as you reported. For this reason, the behavior has been fixed at commit d869af4 to replace it with the default encoding if it determines UTF-7. As a workaround, uncheck the checkboxes listed below in the Codepage category of the Options dialog. A file saved in UTF-7 should be able to be recovered by opening the file with WinMerge and saving it in a different encoding as shown below in the File-> File Encoding menu. Thank you for your report. |
I'm turning this option on\off from time to time (because it works life alpha product). Just didn't check the status bar this time. |
Maybe optional confirmation yes\no message box with detected code page would be appropriate ? |
Most people don't expect the files to be opened in UTF-7. I don't like the message box that appears when I open the files. You can reopen the file in UTF-7 by specifying code page 65000 (UTF-7) from the File-> File Encoding menu item. |
In .sql file saved WinMerge replaces:
If corrupted file is opened to check for differences those differences are not showed.
The text was updated successfully, but these errors were encountered: