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

Add additional legacy encodings #39

Closed
wants to merge 2 commits into from
Closed

Conversation

@inexorabletash
Copy link
Member

inexorabletash commented Apr 1, 2016

An improvement to our indexing and metrics analysis has revealed that we were incorrectly reporting on the use of some legacy encodings. A substantial number of web-exposed resources -- in particular, many generated with older hardware and exposed to the web through non-transcoding proxies -- use encodings not covered by Encoding standard. We believe it will be necessary to add support to browsers (and thus to the Encoding standard) to ensure this content remains accessible and usable.

The additional encodings are:

  • cp037
  • cp500
  • cp875
  • cp1026
  • cp1140

(I was not able to get Anolis running; bit-rot appears to have set in. Someone will need to rebuild Overview.html using the Makefile after merging - sorry about that.)

cp037, cp500, cp875, cp1026, cp1140
@annevk
Copy link
Member

annevk commented Apr 1, 2016

No worries about Anolis. I'll handle that.

  1. encodings.json is not updated.
  2. Labels need to be lowercase.
  3. I wonder if there's a better name for single-byte encodings if we need this new variant.

And obviously this needs review from other implementers, such as @hsivonen. This is a pretty big change.

@annevk
Copy link
Member

annevk commented Apr 1, 2016

Also, these have some serious security implications, since they are not ASCII-compatible. I'm sure how wise it would be to add these. We could reduce the implications a bit by not supporting the encoder, but that doesn't address all issues.

@inexorabletash
Copy link
Member Author

inexorabletash commented Apr 1, 2016

  1. encodings.json is not updated.
  2. Labels need to be lowercase.

Addressed in latest commit.

@vyv03354
Copy link
Collaborator

vyv03354 commented Apr 1, 2016

Gecko has never supported EBCDIC encodings. I don't understand why those encodings are needed for Web compat unless Web==IE.

@inexorabletash
Copy link
Member Author

inexorabletash commented Apr 2, 2016

Now that April 1st is drawing to an end we can close this out. But first I'll quote the Jargon File:

Hackers blanch at the very name of EBCDIC and consider it a manifestation of purest evil.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.