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

Logistics:

* Now we use Travis it might be possible to check in less of the output. The *.txt resources are somewhat special however as I only regenerate those when there is a change and that affects the date they display (which is mostly non-normative given the hash, but seems bad to update all the time).
* If the fonts are generally applicable a better place might be https://github.com/whatwg/resources.whatwg.org.
* A subdirectory seems okay. Again, with Travis and deploying through scp that should be less of an issue now than it used to be.

Accessibility: I was thinking about blind users, though colorblindness matters too of course. I didn't realize you (ab)used language to optimize font selection. I also have no great suggestions here, since these tables are rather involved. Perhaps something to ask stackoverflow/Twitter?

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