You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue
When viewing text files in xed, there is no convenient way to check the file's current encoding (apart from opening the Save As... dialog and checking which encoding is pre-selected there).
Steps to reproduce
Open a text file with content
Try to figure out its current encoding
See that it's only possible in Save As dialog, like described.
Expected behaviour
I would like to see the file's encoding displayed somewhere, preferably in xed's bottom bar.
A plus would be if the same applied to current line ending style.
A double-plus would be if the encoding could be quickly changed from the place where it is displayed (if 'change' should mean overriding the detected encoding and force-opening the file with another encoding, or if that should mean saving the file with the same name but different encoding, or somehow having both of those possibilities would have to be defined and documented.)
Other information
The text was updated successfully, but these errors were encountered:
Issue
When viewing text files in xed, there is no convenient way to check the file's current encoding (apart from opening the Save As... dialog and checking which encoding is pre-selected there).
Steps to reproduce
Expected behaviour
I would like to see the file's encoding displayed somewhere, preferably in xed's bottom bar.
A plus would be if the same applied to current line ending style.
A double-plus would be if the encoding could be quickly changed from the place where it is displayed (if 'change' should mean overriding the detected encoding and force-opening the file with another encoding, or if that should mean saving the file with the same name but different encoding, or somehow having both of those possibilities would have to be defined and documented.)
Other information
The text was updated successfully, but these errors were encountered: