DVITYPE(1)
π dvitype β the manual, but make it make sense π
okay so you're reading the General Commands Manual page for dvitype(1) (and its lil sibling odvitype) and honestly? iconic of you. sit down, grab a boba, we're doing this π§β¨
β¨ NAME β¨
dvitype, odvitype β translate a dvi file for humans to read π«Ά
like. that's the whole job. it takes the unreadable bytes and makes them readable by actual people. slay.
πΈ SYNOPSIS πΈ
dvitype dvi_file[.dvi]
that's it. that's the whole vibe. one file, bestie. π
π¦ DESCRIPTION π¦
so dvitype takes a DVI (DeVice Independent) file β the kind that tex(1) or gftodvi(1) outputs β and translates it into a file that humans can actually read. no cap. π
it's also lowkey doing three jobs at once, main character energy fr:
- it's a DVI file-validating program β like, if
dvitypecan read it, it's correct. that's the vibe check. β - it's an example of a DVI-processing program for future device drivers (so future you can be like "oh THAT'S how we do it")
- and obviously it's the translator
the output can show you all the commands, just the important ones, or none at all β and in that last case it only reports errors. so it's giving "silent but judgmental" and we respect it π
you can also select a subinterval of pages, and you can change the magnification and resolution of the ``output device'' β and so on. so many little knobs, obsessed.
if you omit the .dvi extension from dvi_file, it gets supplied for you. no need to type it, queen. π
the output goes to stdout. π€
and then there's odvitype, which does the exact same job but for Omega/Aleph's output, modified to support their .ofm font format. two sisters, one mission π«Άβ¨
π OPTIONS π
quick note before we dive in: see tex(1) for details of command-line parsing. iykyk.
-dpi=realβ set resolution to real pixels per inch. default is300.0. yes, it's a real number, treat her with respect π-magnification=numberβ override the existing magnification with number. you're in charge now β¨-max-pages=numberβ process number pages. default is one million. ONE MILLION. that's the energy π«Ά-output-level=numberβ verbosity level, from0to4. default4. turn it down if you want peace, turn it up if you want TEA β-page-start=page-specβ start at page-spec, for example2or5.*.-2. pick your starting point, main character that you are π-show-opcodesβ show numeric opcodes (in decimal). numbers! on display! β
the standard -help and -version options are also supported. of course they are. π©·
π ENVIRONMENT π
the environment variable TEXFONTS is used to search for the TFM files used in the DVI file. see tex(1) for the details of the searching. π
if TEXFONTS is not set, it uses the system default. so either way you're covered, bestie π«Ά
π SEE ALSO π
gftype(1)pktype(1)- Donald E. Knuth, TeXware.
- DVI structure topic on CTAN:
https://ctan.org/topic/dvi-struc - Package page on CTAN:
https://ctan.org/pkg/dvitype - Section in the Web2c manual:
https://tug.org/texinfohtml/web2c.html#dvitype-invocation - Typeset source code, including the DVI file format description:
https://ctan.org/pkg/knuth-pdf
π AUTHORS π
Donald E. Knuth wrote the program, based on work by David Fuchs. it was published as part of the TeXware technical report from Stanford. π
Howard Trickey and Pavel Curtis originally ported it to Unix. π»
Yannis Haralambous and John Plaice created the Omega version. π
public discussion list and bug reports: https://lists.tug.org/tex-k β go yell (kindly) π«Ά
okay that's the whole page, you ate that. this was Web2C 2026, dated 22 January 2026 β which is literally the DVITYPE(1) energy. periodt. πβ¨π¦πΈπ
π¦ where this page comes from
- arch rolling: texlive-doc 2026.1-1 Β· GPL
- ubuntu stonking: texlive-binaries 2026.20260303.78225+ds-5ubuntu1 Β· TeX-Live
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms