I'm sorry, but there seems to be a miscommunication.

Probably if on pressing "Reload as" or "Set encoding" a flat list

There can be a lot of encodings, a flat list is likely to be too big for small screens like laptops.

I wrote

Probably if on pressing "Reload as" or "Set encoding" a flat list (...) would pop up with find-as-you type possibility.

Not unfold as a submenu, like now, but pop up as the list of plugins when you select Tools -> Plugins. It brings up the list of all installed plugins but it's not important whether it fits on a small laptop screen because it has a find-as-you-type field, where you type a part of the name of the plugin you want and then select it. If you had to select a plugin from a menu it would be a nightmare. Why not give one the possibility to select encoding in such a way too? Or for that matter the file type too (Document -> "Set file type"). There are a lot of file types and they are also grouped into submenus which makes it tedious to get to any exact file type.

Also (but that is less critical) probably File -> "Reloas as" can be duplicated as "Recode file" adjacent to Document -> "Set encoding"?

As I said above, all files are utf-8 in memory, they only get encoded at save, so there is no "Recode As".

Thank you for the explanation, I understood that all files are utf-8 in memory the first time you said it :)

But there is is a menu item File -> Reload as. What I suggested was making a duplicate of that item as Document -> "Recode file" adjacent to Document -> "Set encoding". Because in practice it does exactly what one would expect from a menu item of that name and it would be more logical to have it near the item "Set encoding". I saw the option "Set encoding", saw that it has no effect on the file that has already been opened with the wrong encoding and did not think to look for a possibility to "reload" the file. If there was an item "Recode file" near to "Set encoding" I would have immediately looked there. It just seems logical from a common user point of view.

Well, not that the second one is critical, but the first one (making a searchable list out of those nested submenus) would, imho, greatly improve usability.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.