bfirsh

If you're on a phone, here's a responsive HTML version: https://www.arxiv-vanity.com/papers/0806.3617/

If you’re on a phone, here’s an HTML version of the paper: https://www.arxiv-vanity.com/papers/1807.07685/

Almost everybody on arXiv provides their LaTeX source which let’s us do things like this: https://www.arxiv-vanity.com

I am from London and lived in the US for a bit. I struggled to navigate. I think it is because I navigate by modelling the shape of the streets. When all the streets are the same shape, that subconscious system stops working.

I also tend to find I underestimate distances in grid systems. I think it’s because in European cities I estimate distance by the number of distinct shapes I can remember on the way there. In a grid, I think my brain smushes all those identical block shapes into one. In a similar way to how time flies when doing a repetitive task.

This is really good for that: https://octobox.io/

If you're on a phone, here's an HTML version of the article: https://www.arxiv-vanity.com/papers/1803.05741/

Discussion from yesterday here: https://news.ycombinator.com/item?id=17208293

Here's an HTML version of the paper if you're on a phone: https://www.arxiv-vanity.com/papers/1608.08225/

I just got a 20 year old Land Rover and, after having attempted to repair consumer electronics and modern vehicles, I am stunned at how easy they are to repair.

Firstly, it is an entirely mechanical car, which makes everything much simpler. But the truly stunning bit is the documentation and community.

All of the workshop manuals are available online. That is good enough for most tasks, but if something particularly complex needs diagnosing, there are forums with all the information you need.

When you need to get parts, an exploded diagram of the entire car is available online with part numbers. Both the original manufacturer and several third parties still make parts. Somebody has even made a price comparison website.[0]

I wish all the things I owned worked like this. I understand the economics often don’t work out for smaller, cheaper things, and there is no incentive for the original manufacturer to provide these things, but surely there is enough of a community to support common repairs in a similar way.

[0] https://www.landroverworkshop.com

If you’re on a phone, here’s an HTML version of the paper: https://www.arxiv-vanity.com/papers/1802.07740/

I will never forget the feeling of awe when I entered that hanger and saw the butt end of the Saturn V. It is really is something that needs to be seen to be appreciated.

And then, after walking quite a distance down the length of the rocket, realising they’ve left out the middle stage because it doesn’t fit in the vast building it is in. I laughed in disbelief.

If you're on a phone, here's an HTML version of the paper: https://www.arxiv-vanity.com/papers/1712.03280/

If you’re on a phone, here’s an HTML version of the article: https://www.arxiv-vanity.com/papers/1712.00676/

Here's an HTML version of the paper:

https://www.arxiv-vanity.com/papers/1712.01815/

Table 2 is broken, but the rest is much more readable if you're on a phone.

If you're on a phone, here's a responsive HTML version of the paper: https://www.arxiv-vanity.com/papers/1710.08864/

So much this. This is one of the main reasons I wanted to build this.

https://github.com/arxiv-vanity/engrafo/issues/127

We haven't implemented many of the LaTeX packages used in papers that aren't machine learning papers yet - sorry. :(

This is fair. If somebody stumbles across this thinking it is how you intended it to be displayed, I can understand you'd be unhappy. We should make it clearer that we're just a conversion tool, not a source.

If you want us to remove your paper and just point at the PDF, we're happy to do so. My email's in my profile if you don't want to post the broken render here!

Yeah, even building upon Pandoc's LaTeX parsing, 3 months of grunt work got us this 20% working. Over the next 12 months we'll get the other 80% working. :)

LaTeX is hard, but we'll keep at it! That issue is being tracked here: https://github.com/arxiv-vanity/engrafo/issues/12

What Arxiv URLs were you trying?

LaTeX is really tricky to parse, which is why you're seeing those "failed to render" errors. Judging from our logs, it works about ~80% of the time. That's up a lot from plain Pandoc though - it could render hardly anything from Arxiv.

Yeah, that's a good point. Andreas's site is a bit out of date. I've made them link to more useful places. Thanks!

A bit of wordplay on our favourite Arxiv tool. :) http://arxiv-sanity.com/

Yes! This is a great idea, and something we have been thinking of. https://github.com/arxiv-vanity/arxiv-vanity/issues/67

Those problems are normally Pandoc parsing errors. Considering it's open source, perhaps we should print the error message so people can actually help fix it...

The MathJax failures are either things that MathJax doesn't support, or use of \DeclareMathOperator which we haven't added support for yet.

Edit: Added a more useful error message. :) https://www.arxiv-vanity.com/papers/1608.04012/

Because we didn't know that existed! That looks so much better, thank you. The pandocfilters library is really hard to use.

https://github.com/arxiv-vanity/engrafo/issues/160

A lot of things. LaTeX and its packages have so much surface area. Our approach so far is to just make the papers that we read readable. That probably covers the 20% of LaTeX features that 80% of people use.

Here is the broken stuff we are keeping track of: https://github.com/arxiv-vanity/engrafo/issues (feel free to add to it!)

Ah, looks like we don't support theorems. You can track it here: https://github.com/arxiv-vanity/engrafo/issues/157

Thanks!

We were frustrated by the experience of reading machine learning papers on screens (particularly phones/tablets). There are lots of good tools for authoring HTML papers (Distill, Authorea, etc) but nothing that deals with the vast number of PDF papers that already exist.

So, we built Arxiv Vanity: a site that renders Arxiv papers as web pages. It’s still pretty janky, but for the papers that do render correctly, the experience is so much better than reading a PDF. For example:

https://www.arxiv-vanity.com/papers/1705.04085v3/

https://www.arxiv-vanity.com/papers/1708.00884/

https://www.arxiv-vanity.com/papers/1705.06031v2/

The source for the LaTeX to HTML renderer is on GitHub[0]. It’s built on Pandoc[1] and Distill.pub’s template[2].

[0] https://github.com/arxiv-vanity/engrafo

[1] https://pandoc.org

[2] https://github.com/distillpub/template

I have a similar setup, but using Docker images instead of Heroku buildpacks. Buildpacks are horrible if you want to do anything custom.

To make this work, I use Codeship instead of Travis. Codeship builds a Docker image, runs the tests against the image, then pushes the image to Heroku if the tests pass: https://documentation.codeship.com/pro/continuous-deployment...