0. There are **no error messages** displayed in my workflow. If I may be ignorant a bit, it _just doesn't work_. But it is a very good idea that user was notified aboud all these limitations when they are encountered (`NULL` value for example). Since Geany is not ashamed of nagging the user (#2863) it is only logical for such notifications (confirmation windows) to be included.
1. I know it's not ASCII, that's why it's in brackets. I would only like to display ASCII symbols and all the other values with special (hex or so) symbols. **Geany doesn't let me do that in any way.** I also stated it's an _8-bit ASCII_, which you conveniently overlooked. As a developer, I'm sure you know what I'm talking about, otherwise just reread my OP and this time overlook the word _ASCII_.
2. I know all that, but what you are trying to present as my issue **is actually Geany's shitty nomenclature, not mine**. I only used it out of my respect for the developers which apparently use it. If I need to be more explicit, Geany has `Without encoding (None)` option in `Document > Set Encoding`. Maybe that is another issue?
3. And that does not seem broken to you, especially if non-Unicode default is set to _no encoding_?
4. I agree. But I'd still expect better handling of this from a versatile text editor (see 0th point above).
5. By "output not changing" I mean that I use the `Document > Set Encoding` function, select a new encoding and **nothing ever changes** after that. For example: If a file is opened as Unicode gibberish, it stays like that no matter which encoding is selected. I've tried this with different files/encodings, always the same, as if the function wasn't there. Can this functionality be broken from outside?
6. I completely agree and that is why I think **one should be able to disable this sporadic encoding-detection black magic altogether** and just have a... you know... a working text editor...