4 ms·
I read the Epsom's Version PDF before the video was released, and the typesetting was absolutely terrible. https://imgur.com/a/wjK5br5 https://imgur.com/a/wjK5
by TapamN 2y ago
I read the Epsom's Version PDF before the video was released, and the typesetting was absolutely terrible.
https://imgur.com/a/wjK5br5 https://imgur.com/a/wjK5br5
After the opening on how he's bothered by minor errors, I thought it had to be part of a joke, and it was a setup for a punchline to be revealed later in the paper. But eventually I realized, no, the PDF must not being displayed the way it was intended. I was reading it in Evince at first, but muPDF gave much better output.
- JadeNB 2y agoHe does mention in the text above the video: > Be warned that due to "BUG", these seem only to display properly in Chrome. I am working on fixing "BUG" once I get some sleep; I have some leads due to helpful people on the blog.
- lupire 2y agoThat's how Android Firefox mangles PDF also.
- snet0 2y agoIt's bizarre to me that different applications display PDFs differently. Isn't one of the primary purposes of PDF to have a consistent typesetting?
- jimbobthrowawy 2y agoPDF is a huge standard and the canonical implementation isn't open source. Still an improvement on postscript by not being as easily turing complete.