Pomax

I've found the simplest solution to be "don't pretend they live on the HOC", and instead have the HOC grant access to the underlying component: ``` var React = require('react');...

That doesn't really disspell the myth though, For the long version I'd go with something like: "OpenType is the font specification, and the name for the "type of font". TrueType,...

oh man, I've not worked on this thing in years - having specs be self descriptive, and yield code that can be queried for this descriptions, sounds like a great...

aye. turning the parser into a true AST builder (probably using the struct.js from the CFF-Glyphlet-Font repo) should solve this problem later, taking out the spaces for now seems imminently...

Can you explain what you mean with "inaccessibility"? If there are broken links, those should be fixed, not just fixed in the CN translation only. Which links didn't work?

thanks for spotting!

In fact, there should not be any `/` at all, it should just link to `#toc`. Good find.

Ah, I see. This is caused by the `` element, which is necessary for correctly resolving images etc.

@ra30r it might be good look at the first two items posted above - the first is probably a small issue, the second one is pretty important for making sure...

Based on https://tex.stackexchange.com/a/835/8406, Linux Libertine should work for adding Cyrillic support on the LaTeX side for maths mode, https://tex.stackexchange.com/a/201244/8406 might be necessary