<story><title>Sysadmin war story: the network ate my font</title><url>http://verticalsysadmin.com/blog/sysadmin-war-story-the-network-ate-my-font/</url></story><parent_chain></parent_chain><comment><author>24gttghh</author><text>Yeah? Try dealing with a printer that has to have a font file sent to it with an lp command from cron every 15 minutes or else checks wont be formatted correctly. AND there is a physical device (either USB on the printer or inline on ethernet in front of the printer) which has the MICR fonts stored.&lt;p&gt;And then the printer you are migrating the MICR device to has decided it doesn&amp;#x27;t understand the PCL in the font file anymore.&lt;p&gt;This is 2017 and I just dealt with this today.</text></comment>
<story><title>Sysadmin war story: the network ate my font</title><url>http://verticalsysadmin.com/blog/sysadmin-war-story-the-network-ate-my-font/</url></story><parent_chain></parent_chain><comment><author>gumboshoes</author><text>This sort of stuff happened all the time when I worked in tech support for ad agencies. Printing font problems seemed to be 99% of the job, some days. PDFs helped — but only of the person making them remembered to embed the fonts. Usually you would simply make an EPS (encapsulated Postscript file), which would work most of the time — as long as the receiving printer had sufficient memory for huge print files. Can&amp;#x27;t tell you how many thousands of times art directors who should&amp;#x27;ve known better would just send Quark or PageMaker or (later) InDesign files without the fonts. In fact, there were (are?) preflighting programs designed just to solve this exact problem. They&amp;#x27;d look at your files and determine: Are your fonts there? Are your images there? How will this print? etc., etc.</text></comment>