-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encoding of decoded text should be easy to change #186
Comments
I think allowing any encoding would be a great plus. I would like to use this extension together with the zowe explorer extension. The zowe explorer allows handling datasets from IBM mainframe z/OS. These datasets come with all different ebcdic encodings. Full text datasets are translated during download but datasets which combine text with non text data can't be converted and must be downloaded in binary form. Browsing with hexeditor is ok for the hex part of the display but not for the decoded part because it does not take the encoding from z/OS. I know the encoding but can't tell hexeditor about it so it shows wrong decoded characters. |
Similar: #187 |
Hi We need support for EBCDIC files. Some are parts of Git repository (declared binary in .gitattributes and stored "as is"). It exists many EBCDIC encoding:
|
Is it currently possible to change the encoding (code page) of the decoded text? I can't find a way. How to do it? |
Upon reflection, the hexadecimal interpretation of a file should be based on the encoding choice defined in the VS Code editor.
To change the interpretation, you must change the encoding associated with the file in VS Code. As for files from a system with an encoding not supported by VS Code, in particular EBCDIC files, often containing a mixture of display characters (convertible) and non-displayable bytes (non-convertible), retrieved from an IBM z/OS system without conversion, then we must use a hexadecimal interpreter specific to the management of these files. Thanks. |
It should be easy to switch between different text encoding for the decoded text. Encodings should contain at least
Preferably more encodings would be helpful, e.g. UTF-16 and ISO Latin 9 (ISO 8859-15)
The text was updated successfully, but these errors were encountered: