Community
Participate
Working Groups
3.0 RC1 VM: IBM JDK 1.4.1 (does not happen with Sun's VM, because it tolerates invalid encodings silently) Steps to reproduce: 1 - Create a simple project 2 - Create a text file (file.txt), write a simple string like: "this is a test" 3 - Close the editor 4 - change the project encoding to be UTF-16 5 - try opening the file with the text editor - it will fail because the contents cannot be read using the configured encoding (this behavior is IBM-specific) 6 - leaving the "Error editor" opened, open the file using the system editor (Notepad?), make some changes, save and close 7 - back to Eclipse, only closing the "Error editor" will cause the dialog that prompts the user whether the external changes should be loaded. Dismiss the dialog choosing whatever option you want. 8 - try opening any file in the workspace using the text editor - it will always fail with no feedback to the user (no message, no log entry), just stops working
*** This bug has been marked as a duplicate of 66357 ***