Skip to content
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

Support EBCDIC encodings #49891

Closed
ind1go opened this issue May 15, 2018 · 3 comments
Closed

Support EBCDIC encodings #49891

ind1go opened this issue May 15, 2018 · 3 comments
Labels
feature-request Request for new features or functionality file-encoding File encoding type issues *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@ind1go
Copy link

ind1go commented May 15, 2018

There are no EBCDIC encodings available in the encoding chooser when opening a file, making it impossible to read files in EBCDIC encodings like cp37 and cp1047.

πŸ™‹β€β™‚οΈ I'll happily take a look at this if someone can point me in the right direction to get started!


  • VSCode Version: 1.23.0
  • OS Version: MacOS

Steps to Reproduce:

  1. Open a file which is in an EBCDIC encoding
  2. ⌘+⇧+P to open the command palettle
  3. Change File Encoding -> Reopen with Encoding
  4. Weep when no EBCDIC options are displayed in the list 😒

Does this issue occur when all extensions are disabled?: Yes

@bpasero bpasero added feature-request Request for new features or functionality file-encoding File encoding type issues labels May 16, 2018
@bpasero bpasero removed their assignment May 16, 2018
@bpasero
Copy link
Member

bpasero commented Sep 11, 2018

Depends on ashtuchkin/iconv-lite#111

@bpasero bpasero added upstream Issue identified as 'upstream' component related (exists outside of VS Code) and removed feature-request Request for new features or functionality labels Sep 11, 2018
@joaomoreno joaomoreno added the feature-request Request for new features or functionality label Sep 12, 2018
@vscodebot vscodebot bot added the *out-of-scope Posted issue is not in scope of VS Code label Oct 8, 2019
@vscodebot
Copy link

vscodebot bot commented Oct 8, 2019

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality file-encoding File encoding type issues *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

3 participants