![]() ![]() ![]() install gv through MacPorts or Fink, or MacGSView from here, or MacGhostView, or ($22) PostView. Of course, if you're not generating the PS yourself, then the simple answer is that Preview sucks, and you should use a better PostScript viewer instead, e.g. a couple of other unlikely reasons, such as Ghostscript being too old.Īlso, look at the testflow package, which is a ‘diagnostic suite which is designed to test LaTeX "print work flow" and to provide lots of helpful information ’.So force the PS file to use Type 1 fonts, by generating it as: dvips -Ppdf myfile -o myfile.psįonts go fuzzy when you switch to T1: If you have \usepackage, that might be a problem.("Note that the font encoding T1 has nothing directly to do with the font format Type 1".) There are fixes. The problem is that dvips's default is to embed Type 3 fonts, and the PDF viewer probably does a bad job of displaying bitmapped fonts. However, many people still want to edit documents using more familiar programs like Office or other software, which can be a problem with PDFs. before Adobe Reader 6, released in mid-2003). The wrong type of fonts in PDF: This is apparently the most common in older versions of PDF viewers (e.g. If you must go through PostScript, see the Quality of PDF from PostScript at the UK TeX FAQ, which points to a few common reasons why the PDF might be fuzzy: (This "blurry" problem is also common in PDF files that have been generated from PS.) The best fix is to use pdflatex directly. The problem happens because Preview converts from PS to PDF before displaying it.Nevertheless, if you're trying to read it on screen, "it will look fine in print" is not much of a consolation. it's probably just the viewer (Preview), and printing it will look fine. ![]() I've been bothered by this too, so I looked it up just now. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |