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

Why is that called a stride?

Currently all indexes require this to be found out to some extent by implementers. The encoder/decoder algorithms have some hits about the ranges in play (or hard limits, if you will), but no detailed information geared in that direction.

I'm not opposed to adding it, given that it's unlikely we're tweaking these indexes (much) going forward, but it would be good to know where you would expect that information and how valuable it would be for me to put effort into finding it out. (I don't recall from memory unfortunately.)

-- 
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-260963187