thecodeviking

6 ms·

1. 1.▲
   by thecodeviking 9y ago

   Yea, it's tough work. We're hoping to invest more in the conversion library (and support the Engrafo's team to do so). It's going to take a lot of time and elbow grease to get it to where it needs to be!
2. 2.▲
   by thecodeviking 9y ago

   Definitely, thanks!
3. 3.▲
   by thecodeviking 9y ago

   +1 to what @undefined said. If all goes well, we hope to act as a front-facing host for the Engrafo engine. That'll enable the ArXiv Vanity team to focus their efforts on improving the conversion process (which is what they'd lik
4. 4.▲
   by thecodeviking 9y ago

   It's not that different, at the moment. The only real difference is that we're pre-computing the HTML so it's faster (ArXiv Vanity runs at request time). We've talked a lot with the ArXiv Vanity team. If all goes well
5. 5.▲
   by thecodeviking 9y ago

   Yup, @kpsns nailed it. LaTeXML does the heavy lifting in converting TeX to XML. From there some post processing does the job of converting it to a nice responsive template (that's done by Engrafo / the ArXiv Vanity team). We lov
6. 6.▲
   by thecodeviking 9y ago

   Hi HN, I'm an engineer on the Semantic Scholar team that worked on integrating this feature into the site. Here's a blog post that talks a bit more about what we're doing: https://blog.semanticscholar.org/anno
7. 7.▲
   Announcing a new way to read papers(blog.semanticscholar.org)

   1 points by thecodeviking 9y ago|0 comments