dvipdfm

dvipdfm
Name	dvipdfm
Author	Mark A. W. Lawrence
Initial release	1993
Latest release	2002 (dvipdfm)
Operating system	Unix-like, Microsoft Windows via ports
License	GNU General Public License

dvipdfm

dvipdfm is a software utility that converts DVI files produced by Donald Knuth's TeX engines into PDF documents compatible with Adobe Systems' PDF viewers and printers. It was developed to bridge outputs from TeX Live, LaTeX, Plain TeX, ConTeXt, and AMS macro packages to workflows involving Adobe Acrobat, Ghostscript, and PDF-centric publishing pipelines used by Springer, Elsevier, IEEE, and academic institutions. The tool influenced later projects and integrations with distributions such as MiKTeX and utilities in GNU toolchains.

History

dvipdfm originated in the early 1990s as a response to demand from users of Leslie Lamport's LaTeX and Donald Knuth's TeX for direct DVI-to-PDF conversion without intermediate PostScript produced by dvips. Its development paralleled work by authors and maintainers in projects like Karl Berry's TeX Live and collaborations with developers in TUG communities and user groups associated with universities such as Stanford University, Massachusetts Institute of Technology, Harvard University, and University of Cambridge. Over time, dvipdfm's approach and features intersected with efforts from projects led by figures including Hermann Zapf, Leslie Lamport, Frank Mittelbach, Donald Knuth, and teams at Microsoft Research and Adobe Systems. The emergence of pdfTeX and later LuaTeX and XeTeX shifted ecosystems; distributions maintained both dvipdfm and pdf-producing TeX engines to support legacy workflows at publishers like Wiley, Oxford University Press, and Cambridge University Press.

Features

dvipdfm provided glyph embedding and font subsetting compatible with Type 1 fonts used by foundries such as Monotype Imaging, Linotype, and vendors like Adobe. It supported inclusion of graphics via standards used by Richard Stallman's GNU Ghostscript and image formats processed by John Warnock's PostScript ecosystem. Metadata handling allowed tagging used by indexing services including CrossRef, ORCID integrations common at National Institutes of Health, and bibliographic workflows used by EndNote, Zotero, and Mendeley. The utility implemented PDF features comparable to those in tools from Apple Inc. and Microsoft Corporation, such as annotations, hyperlinks, and outline bookmarks used in publishing by organizations like NASA, CERN, ESO, and IEEE. It also offered support for CID-keyed fonts for Asian scripts, impacting localization efforts by institutions including Kyoto University, Peking University, and Beijing University of Aeronautics and Astronautics.

Usage

Typical usage invoked dvipdfm after running TeX or LaTeX engines to produce a .dvi file, then converting to PDF for distribution via services like arXiv or university repositories at Stanford Digital Repository and Harvard DASH. Command-line invocation followed patterns familiar to users of Unix shells like those on FreeBSD, NetBSD, OpenBSD, and Linux distributions such as Debian, Ubuntu, Fedora, Red Hat Enterprise Linux, and Arch Linux. Windows users integrated dvipdfm through distributions like MiKTeX and projects maintained at CTAN mirrors used by researchers at MIT, Caltech, and ETH Zurich. Workflows often combined dvipdfm with post-processing tools maintained by communities around TeX Live, TeXworks, TeXstudio, Overleaf, and ShareLaTeX.

Compatibility and Integration

dvipdfm interoperated with font technologies from Adobe Type Manager, OpenType, and TrueType vendors, aligning with printing infrastructures at companies like HP, Canon, and Epson. It was integrated into publishing pipelines used by academic publishers including Nature Publishing Group, Cell Press, and PLOS. Integration points existed with bibliographic processors such as BibTeX and biber, indexing services run by PubMed and Scopus, and digital repositories operated by WorldCat and Library of Congress. The tool fit into continuous integration systems used by research groups hosted on platforms like GitHub, GitLab, and Bitbucket for automated typesetting in scholarly production.

Development and Maintenance

Primary development was led by Mark A. W. Lawrence with contributions from volunteers across the TeX Users Group community and maintainers of CTAN packages. The project was discussed and supported on mailing lists frequented by contributors associated with institutions like University of Illinois, Princeton University, Columbia University, University of Oxford, and University of Cambridge. As newer engines such as pdfTeX, LuaTeX, and XeTeX matured, active development of dvipdfm slowed; successors and forks addressed new Unicode, OpenType, and microtypography features demanded by academics at Harvard, Yale University, Princeton, and national labs like Argonne National Laboratory.

Security and Licensing

dvipdfm was distributed under the GNU General Public License which aligned with policies used by Free Software Foundation and projects hosted by GNU and FSF affiliates. Security considerations involved sanitizing embedded objects to mitigate issues relevant to PDF viewers from vendors like Adobe Systems and open-source projects such as Evince, Okular, and SumatraPDF. The licensing model facilitated inclusion in distributions maintained by Debian Project and Free Software Foundation Europe and compliance with institutional policies at repositories like Zenodo and Figshare.

Category:TeX