Your comments
I think this use case should be handle in a way close what Eclipse editor does: if the file contains characters that may not be encoded with the specified encoding, the editor should refuse to save and offer an option to go to the first incompatible character, in order to allow the user to change it.
What will happen if I open another file specifying ISO LATIN and then add incorrect character and try to save ? Will it automatically switch to another encoding ? Or will refuse to save ? Or will it remove the wrong characters ?
And if I remove the wrong characters from the first file, will the editor accept to switch back to ISO LATIN encoding ?
Fantastic editor anyway, and thanks for being so fast to answer questions!
Changing the encoding for saving the document seems not to work. I oppened an ISO Latin document by error as an UTF8, and it was converted to UTF8. After saving to my server, the encoding was broken (UTF 8 instead of original ISO LATIN) so I changed to ISO LATIN in the document properties and saved it again, but it still UTF 8 and in document properties, ISO LATIN as been reset to UTF 8 :-(
Customer support service by UserEcho
Here is the exact use case:
I opened a file (through SSH) that was encoded in ISO Latin. I then added some code, including the Euro character. Then I saved the file (not having taken care of encoding at that time). When I tested the file on the server, all accented characters were broken and I realized the file had been saved in UTF-8, although I supposed it had been opened in ISO-LATIN. This is what make the editor unusable in our case. It is not considered acceptable that the editor changes the encoding without warning the user. As I said, the Eclipse editor, in such a case, would display a dialog box saying it can't save the file because of special characters, as many (most?) other editors would do. Eclipse offers one significant advantage upon some editor by offering an option to go to the first occurrence of such a character.
Beside that, I would have thought of a intuitive workaround to correct the problem: reopening the file, removing the erroneous characters and saving it with the old encoding. From what you said earlier, it seems it is not possible, but your last message seems to imply the contrary. If possible, this would be an acceptable workaround until a best fix, although it has the great inconvenient to let the server serve a wrong file during while the workaround is applied. But if it is not possible, it implies opening the file with another editor able to automatically do this. (The file contain hundreds of accented characters that cannot be manually changed form a tablet editor!)