Timeline for Why does the arXiv produce a messed-up DVI when the PDF is fine?
Current License: CC BY-SA 2.5
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10, 2011 at 17:28 | vote | accept | Ben Webster♦ | ||
| May 1, 2010 at 2:00 | comment | added | Dmitri Pavlov | @Andrew: As I pointed out in my other comment, few TeX documents use PDF-specific features, so when FFF comes out it will probably be incompatible with PDF-specific TeX and the latter will suffer the fate of ChiWriter and troff, which were replaced by completely incompatible system TeX. I am also familiar with evolution of HTML and in my opinion it disproves your statements. Just look how they discarded all presentational elements from HTML and replaced them by CSS. | |
| May 1, 2010 at 1:56 | comment | added | Dmitri Pavlov | @Andrew: As for your first comment, you are obviously trying to start some kind of holy war here. All your statements remain true for me if I replace TikZ by METAPOST, so what's the point of your comment? | |
| Apr 30, 2010 at 16:05 | comment | added | Ben Webster♦ | Interestingly, I hadn't even noticed the font mismatch until now. The Computer Modern math fonts are so thoroughly burned into my brain as "what printed math looks like" that it seemed natural to have them there. Now that I've compiled the file using palatino math fonts as well, it's screwing with my head (look at the version on my webpage if you want it to screw with yours as well: math.mit.edu/~bwebster/TP-KM.pdf). | |
| Apr 30, 2010 at 6:32 | comment | added | Andrew Stacey | And to comment on the future formats: any decent future format will have to be constructed so that anything that works with PDF will work with the future one - otherwise no-one will use it! So just as any tex file that works with DVI will work with PDF, so also any that work with PDF will work in FFF (Fantastic Future Format). Just look at the evolution of HTML to see how this works in practice. | |
| Apr 30, 2010 at 6:30 | comment | added | Andrew Stacey | And we should all just use pure HTML with no CSS, javascript, MathML ... Indeed, we should be using lynx and not firefox. TikZ is fantastic. You can do great things with it, it's easy to use, and it just works! And the TikZ guys write fantastic documentation. I've never tried metapost and probably never will. I've seen some great stuff done by writing postscript directly, but while I could say "Wow, that's fantastic", I could also say "But I'll stick with the easy stuff.". | |
| Apr 29, 2010 at 22:46 | comment | added | Dmitri Pavlov | Can you please point me to the relevant page in TikZ' documentation, especially “why this cannot be done automatically”? Thanks. I must admit that I have no idea how to interpret your statement “there is no standard way of providing fonts with a DVI file”. Just put the fonts in the same directory as the DVI file. For your information, if the DVI file uses any external pictures, the arXiv will give you a tar.gz archive containing the DVI file itself and all files with pictures. This archive should also include all non-standard fonts. | |
| Apr 29, 2010 at 22:22 | comment | added | Mariano Suárez-Álvarez | TikZ's docs explain how to get Postscript embedded into the DVI file, by setting the output driver correctly, and it also explains why this cannot be done automatically. Since there is no standard way of providing fonts with a DVI file, the only portable DVI files are those that depends only on the standard CM family: that may be enough for some people, but it is not enough for others, and therefore the portability is of rather limited use, just as as ASCII is essentially problem-freen unless you need to write in one of the languages 95% of the world writes in! | |
| Apr 29, 2010 at 22:08 | history | answered | Dmitri Pavlov | CC BY-SA 2.5 |