0. When opening `break.txt` the message `The file "breaks.txt" does not look like a text file or the file encoding is not supported.` appears in the status bar. That could be changed to a dialog, but compared to #2863 not opening is not a data loss situation, so I expect thats why no dialog has been created to date.
1. Geany is a text editor, not a binary or hex editor. There are already hex editors available and although its been requested nobody has found enough benefit to do the work to add the facility to Geany (noting its actually likely to be a considerable amount of work). 2. Being rude is not a good way to get volunteers who build software in their own time to do something. I said that possibly the label on the setting might be considered as misleading, suggesting a constructive alternative would be useful, not complaining in bold type. 3. As I have explained, there is no way to load files other than by conversion to UTF-8, anything else is a complete re-write of the editor and unlikely to happen. So trying to find an encoding that works is a useful process for most users. 4. Whatever the expectations, its not the case and isn't likely to change anytime soon. 5. As I explained, the buffer in memory is always UTF-8. So encoding only comes into loading and saving files, nothing in the buffer will change when you select to save it as a different encoding so the display won't change. 6. As I said above Geany edits text, not binary, and text is always encoded, there has to be some agreement that 0x20 is a space, thats what encoding is, there is no way of "disabling" encoding, thats not how text works. For text the reference is the Unicode standard, so the buffer is Unicode and specifically in UTF-8. What you seem to be wanting is a binary editor, and as I have said, Geany is not that. I tried Gedit and it complains about the encoding of all three cases too. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2910#issuecomment-930097126
