CP437 Encoder/Decoder about text-encoding HOT 4 CLOSED

That's a discussion better suited to the Encoding standard:

https://encoding.spec.whatwg.org/
https://github.com/whatwg/encoding/issues

Other than the non-standard encoding capability (which is here primarily to validate the spec) I don't want to introduce anything not covered in Encoding.

(And the Encoding standard is trying to be as limited as possible - unless existing Web content demands it we are extremely unlikely to support any new encodings.)

from text-encoding.

@inexorabletash I understand... Would you be willing to clarify the questions regarding the structure of encoding-indexes so that I'd be able to add it in my own fork?

from text-encoding.

The existing indexes are defined in the Encoding Standard, https://encoding.spec.whatwg.org/#indexes

Basically the index for an encoding is a resource to make the decoder/encoder handler something other than a huge switch statement.

The decoder handler just takes the input byte (or bytes) does math to get an index pointer, and looks up index[pointer]. For CP437 you could just have 256 entries (the 95 printable ASCII ones would have value == index) or you could be more clever and do math to avoid those 95 values. I'd keep it simple, honestly.

The encode handler does the reverse - looks up the Unicode code point in the table (inefficiently!), and if found it returns the corresponding index, then does math to convert that to a byte. Again, if you go with a simple 256 entry table then it's just the index itself as the output byte.

Hope that helps!

from text-encoding.

@inexorabletash thanks, will look into this from here...

from text-encoding.