Live data from Hacker News

Show HN: Read ArXiv Papers on Semantic Scholar as Responsive HTML Documents

semanticscholar.org

1–10 of 16 posts

Re: Show HN: Read ArXiv Papers on Semantic Scholar as Responsive HTML Documents

#2
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/announcing-a-new-way-to-rea...

I'm around to answer questions / discuss the approach. We're super excited and would love to hear your feedback!

Re: Show HN: Read ArXiv Papers on Semantic Scholar as Responsive HTML Documents

#3
Very nice! I like how the HTML rendering is responsive and allows you to read on narrow screens.

MathJax seems to handle most things, but not 100%: https://www.semanticscholar.org/paper/Quantum-Broadcast-Chan...

What are you using for parsing the LaTeX --> (HTML+MathJax) conversion?

Re: Show HN: Read ArXiv Papers on Semantic Scholar as Responsive HTML Documents

#4

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/announcing-a-new-way-to-rea... I'm around to answer questions / discuss the approach. We're super excited and would love to hear your feedback!

Feature idea 1: perhaps you could make references section in the bottom render links, at least for references that provide and arXiv identifier.

Feature idea 2: better/shorter URL structure, the current URL https://www.semanticscholar.org/paper/{title}-{authors}/{uui... ends up quite long and unreadable (may be good for SEO though). If you're rendering mostly arXiv papers you could setup a short URL scheme that mirrors the arXiv url paths: e.g if original URL is https://arxiv.org/abs/XXXX.YYYY your URL could be https://www.semanticscholar.org/paper/arxiv/XXXX.YYYY

Good stuff!

Re: Show HN: Read ArXiv Papers on Semantic Scholar as Responsive HTML Documents

#5
post #3

Very nice! I like how the HTML rendering is responsive and allows you to read on narrow screens. MathJax seems to handle most things, but not 100%: https://www.semanticscholar.org/paper/Quantum-Broadcast-Chan... What are you using for parsing the LaTeX --> (HTML+MathJax) conversion?

The main workhorse is https://dlmf.nist.gov/LaTeXML/ as you can find once you reach https://github.com/arxiv-vanity/engrafo.

LaTeXML converts tex to XML by running latex ("only latex can parse latex") and working on the DVI output.

But nevertheless this is a hard job so I will loook into the engrafo code soon because I want to apply this to a book we have written.

Re: Show HN: Read ArXiv Papers on Semantic Scholar as Responsive HTML Documents

#7
I would recommend that rather than copying "arXiv-Vanity", your team should focus on improving and contributing to "Engrafo" since there are many errors in the HTML conversion. And, leave everything at "arXiv-Vanity" since there is no point of having 2 different places doing the same exact thing.

Re: Show HN: Read ArXiv Papers on Semantic Scholar as Responsive HTML Documents

#8
post #4

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/announcing-a-new-way-to-rea... I'm around to answer questions / discuss the approach. We're super excited and would love to hear your feedback!

Feature idea 1: perhaps you could make references section in the bottom render links, at least for references that provide and arXiv identifier. Feature idea 2: better/shorter URL structure, the current URL https://www.semanticscholar.org/paper/{title}-{authors}/{uui... ends up quite long and unreadable (may be good for SEO though). If you're rendering mostly arXiv papers you could setup a short URL scheme that mirro…

(I also work on the Semantic Scholar team)

1. Totally agree. We know how we can / will do this and plan to do so given enough interest in the MVP reading experience.

2. The url structure is indeed for SEO purposes. (We get a large majority of users discovering our paper pages through organic search)

Re: Show HN: Read ArXiv Papers on Semantic Scholar as Responsive HTML Documents

#9

I would recommend that rather than copying "arXiv-Vanity", your team should focus on improving and contributing to "Engrafo" since there are many errors in the HTML conversion. And, leave everything at "arXiv-Vanity" since there is no point of having 2 different places doing the same exact thing.

We plan to do both. We want to give back to Engrafo where it makes sense, but we also have a unique opportunity given our other semantic features along with the paper metadata from our corpus to build upon this experience. This release is an MVP reading experience, but in the future we plan to add a number of things like: user highlighting, direct linking to authors and citations, and collaborative commenting.

Re: Show HN: Read ArXiv Papers on Semantic Scholar as Responsive HTML Documents

#10
post #5
post #3

Very nice! I like how the HTML rendering is responsive and allows you to read on narrow screens. MathJax seems to handle most things, but not 100%: https://www.semanticscholar.org/paper/Quantum-Broadcast-Chan... What are you using for parsing the LaTeX --> (HTML+MathJax) conversion?

The main workhorse is https://dlmf.nist.gov/LaTeXML/ as you can find once you reach https://github.com/arxiv-vanity/engrafo . LaTeXML converts tex to XML by running latex ("only latex can parse latex") and working on the DVI output. But nevertheless this is a hard job so I will loook into the engrafo code soon because I want to apply this to a book we have written.

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 love OSS at AI2, and are looking to collaborate with the Engrafo / ArXiv Vanity team as we expand the functionality.

Post reply on HN