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

> I like the idea of hosting the index visualizations and I'm on board with your suggestions.

Cool.

> However, I would appreciate it if you could write the PR since I suspect it would be way easier for you to do at this time.

I'll work on a PR.

Is it OK to check in the fonts? In a fonts/ directory maybe? Should I check in the output .html files? It seems that the other generated files are checked in. Should I use a subdirectory?

> One thing that needs to be addressed with the index visualizations I think is that we also include the color coding in a different way. Perhaps by including information in the title attribute?

So far, I've used the visualizations to aid better implementations of gb18030, euc-kr and euc-jp jis0208 decode. At this point, I'm going to take a break to redo the visualizations without the tooltips before I finish the Japanese encodings, and I wish I'd have stopped to do that sooner. Having to hover the cells to see the code point and pointer values is bad.

So I'd prefer a solution that doesn't involve the title attribute.

What problem are you trying to solve by introducing redundancy for color? Color blindness or also blindness? For color blindness, I wonder if there's a set of suitable set of distinguishable colors that works with the known variants of color blindness. (I'm too uninformed about the topic to know whether that's possible.) If some non-color indicators are added, I'd like to use something that doesn't get exported to the clipboard if you select multiple cells and copy them to the clipboard.

For completely non-visual use, there are more potential problems to solve: For example, you might want a screen reader to read the numbers in the language of the user, but the language of the HTML is declared to whatever optimizes Firefox font selection if you've turned Web Fonts off.

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