Re:Sysadmin war story: the network ate my font
by gumboshoes on Friday September 15, 2017 @02:55PM
(#15259720)
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't tell you how many thousands of times art directors who should'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'd look at your files and determine: Are your fonts there? Are your images there? How will this print? etc., etc.
[ Parent
| on HN ]
Re:Sysadmin war story: the network ate my font
by semi-extrinsic on Friday September 15, 2017 @03:39PM
(#15260114)
There are indeed PDF preflight tools to this day. E.g. on Linux you can run `pdffonts` and check that everything is embedded. I believe it's still very common, to the point that my local university's PhD thesis print delivery checklist includes it.
Re:Sysadmin war story: the network ate my font
by noir_lord on Friday September 15, 2017 @05:50PM
(#15261069)
Scribus (DTP program for Linux I love) has it built right in and it's good.
They also pride themselves on the quality of PDF output (and have full (iirc) support for PDF-A).
Re:Sysadmin war story: the network ate my font
by qznc on Saturday September 16, 2017 @10:15AM
(#15264734)
There is nothing popular and free though. I built a simple one myself some time ago: https://bitbucket.org/qznc/vorflug
The font check alone can be done in a few lines of Python: http://beza1e1.tuxen.de/articles/preflight.html