This is an issue that comes up every now and then, for example when you create a PDF file that’s designed for actual printing (like in a book). The fonts used by PDF (or PS) files can be either embedded or simply “linked” to fonts already installed on the system. The advantage to linking is that the file size can be a lot smaller; the PDF file doesn’t need to carry around a full description of how to render each font. Unfortunately, the destination system doesn’t always have the fonts you want. The safest solution is to embed every font description in the PDF file.<\/p>\n
But how do you make this magic happen? There are two important steps I learned about today. (These apply to linux\/unix\/Mac systems.)<\/p>\n
\n1. Tell pdflatex, dvips, and dvipdf to embed the fonts.<\/b><\/p>\n
\nThe best instructions I’ve seen for this are here<\/a>. Basically, you run `updmap` to find out where your config file is, then edit it to indicate that you want the fonts to be embedded. Re-run `updmap` to make those config settings stick, and then you can do pdflatex or dvips or dvipdf (as desired) to create files with embedded fonts.\n<\/p><\/blockquote>\n
That will get you most of the way there. However, if you’re including figures (say, .eps files) that also have their own fonts that weren’t embedded, and those font names aren’t recognized, you may get an error like:
\n
\ndvips: Font Helvetica used in file fancy_widget.eps is not in the mapping file.
\n<\/tt>
\nYou can’t embed the font if your system doesn’t have a mapping for it. Oops! This usually happens with fonts like Helvetica, Times, and Symbol; these are proprietary font names, so their mappings aren’t found in most open source systems. But you can fix this problem, as described in this excellent font reference<\/a>, by replacing the font names with their open-source equivalents:<\/p>\n\n2. Replace proprietary font names with their open-source equivalents.<\/b><\/p>\n
\nSince .eps is a text format, you can just open the .eps file in a text editor and search\/replace the font names. Markus Neteler makes this even easier with a handy bit of sed:
\n
\n cat original_graphics.eps | sed 's+Times-Bold+NimbusSanL-Bold+g' |\\
\n sed 's+Times-Roman+NimbusSanL-Regu+g' |\\
\n sed 's+Times+NimbusSanL-Regu+g' |\\
\n sed 's+Helvetica-BoldOblique+NimbusSanL-BoldItal+g' |\\
\n sed 's+Helvetica-Oblique+NimbusSanL-ReguItal+g' |\\
\n sed 's+Helvetica-Bold+NimbusSanL-Bold+g' |\\
\n sed 's+Helvetica-Bold-iso+NimbusSanL-Bold+g' |\\
\n sed 's+Helvetica+NimbusSanL-Regu+g' |\\
\n sed 's+Helvetica-iso+NimbusSanL-Regu+g' |\\
\n sed 's+Symbol+StandardSymL+g' > new_graphics.eps
\n<\/tt>\n<\/p><\/blockquote>\nFor the particular file I was working on today, a couple of additional fonts didn’t show up on Markus’s list. They were all variants on the Courier font. After some hunting around, I figured out that Courier is “Nimbus Mono L”, so here’s the translation:
\n<\/p>\n \n
\n Courier<\/td>\n NimbusMonL-Regu<\/td>\n<\/tr>\n \n Courier-Bold<\/td>\n NimbusMonL-Bold<\/td>\n<\/tr>\n \n Courier-Oblique<\/td>\n NimbusMonL-ReguObli<\/td>\n<\/tr>\n \n Courier-BoldOblique<\/td>\n NimbusMonL-BoldObli<\/td>\n<\/tr>\n<\/table>\n<\/table>\n <\/center><\/p>\n
Finally, you may want to check the file to confirm that the fonts were embedded. It seems that you can use a utility called ‘pdffonts’ to do this from the command-line, but I don’t have it on my system. Alternatively, you can fire up Adobe Reader, go to “File->Document Properties”, click on the “Fonts” tab, and browse to see that each font is marked “embedded.”<\/p>\n","protected":false},"excerpt":{"rendered":"
This is an issue that comes up every now and then, for example when you create a PDF file that’s designed for actual printing (like in a book). The fonts used by PDF (or PS) files can be either embedded or simply “linked” to fonts already installed on the system. The advantage to linking is […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[23,2,27],"tags":[],"_links":{"self":[{"href":"https:\/\/www.wkiri.com\/today\/index.php?rest_route=\/wp\/v2\/posts\/60"}],"collection":[{"href":"https:\/\/www.wkiri.com\/today\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wkiri.com\/today\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wkiri.com\/today\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wkiri.com\/today\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=60"}],"version-history":[{"count":0,"href":"https:\/\/www.wkiri.com\/today\/index.php?rest_route=\/wp\/v2\/posts\/60\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wkiri.com\/today\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=60"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wkiri.com\/today\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=60"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wkiri.com\/today\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=60"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}