Re: [whatwg/encoding] Inform readers about the structure of the sparsity of index-euc-kr (#78)

We used to have a less sparse index until I opted for simplicity in https://www.w3.org/Bugs/Public/show_bug.cgi?id=16691. 4b20cf61260ed00357663755886d9f7617d60b35 suggests that originally we had this pairing of bytes and then mapped that to pointers:

Lead: 0x81 to 0xC6
Trail: 0x41 to 0x5A, 0x61 to 0x7A, 0x81 to 0xFE

Lead: 0xC7 to 0xFE
Trail: 0xA1 to 0xFE

Perhaps we should indicate for multi-byte encodings what constitute (potentially) valid byte patterns?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/78#issuecomment-261178631