OFM2OPL(1)

πŸ’– OFM2OPL β€” the ofm2opl girlies' guide πŸ’–

okay so bestie, welcome to ofm2opl, a General Commands Manual entry, and honestly? it's giving "quiet little converter that does the most." πŸ¦‹


✨ NAME ✨

ofm2opl β€” convert Omega and TeX font-metric files to property-list files πŸ’…


🌸 SYNOPSIS 🌸

ofm2opl [options] ofmname[.ofm] [oplfile[.opl]]

like. that's it. that's the whole vibe. πŸŽ€


πŸ‘‘ DESCRIPTION πŸ‘‘

so what does she actually do, you ask? ofm2opl translates a binary Omega Font Metrics file, ofmname, into a human-readable property-list form. yes, she's a translator, she's bilingual, she contains multitudes. πŸ’–

by default the program writes to standard output, or β€” if you're feeling fancy β€” to a file you specify as oplfile. your choice, your main character moment. ✨

and plot twist: the program also works with TeX TFM files, producing TeX PL files. versatile queen. πŸ‘‘


πŸ’… OPTIONS πŸ’…

(Same as ovf2ovp.) β€” no cap, that's what the manual says.
  • -charcode-format=type β€” output character codes according to type, and type can be hex, octal or ascii. the default is hex. and ascii? that one says use ASCII for letters and digits, but hex for all else. she's picky like that. πŸ’€
  • -char-format=stype β€” output character codes according to stype, either num or ascii. default is num. ascii works just like in -charcode-format. and bestie, listen: these two options are redundant and both exist only for historical compatibility. periodt. 🫢
  • -num-format=ntype β€” output numbers according to ntype, either hex or octal; the default is hex.
  • -text-format=ttype β€” output coding scheme and family according to ttype, either mixed or upper case; the default is mixed.
  • -help β€” display a brief summary of syntax and options. the "girl help" but make it documentation. πŸ™ˆ
  • -verbose β€” display progress reports. she's narrating her own journey. πŸŽ€
  • -version β€” output version information and exit. dramatic exit, as always. πŸ’…

πŸ“ FILES πŸ“

  • OFMNAME β€” an Omega Font Metric file 🌸
  • OPLFILE β€” an Omega Property List file πŸ¦‹

😭 BUGS 😭

found a bug? email bug reports to <https://lists.tug.org/tex-k> (that's a mailing list), and ngl it's also good to check if the same bug is present in tftopl(1) β€” like, is it her fault or is it a family thing? πŸ’€

and if you just wanna chat about Omega (and Aleph) in general, that happens on the <https://lists.tug.org/omega> mailing list. come hang out, the group chat is open. 🫢


🌈 SEE ALSO 🌈

omega(1), aleph(1), opl2ofm(1), pltotf(1), tftopl(1).

(the whole friend group. iconic.) ✨


πŸ’œ AUTHOR πŸ’œ

so, according to the WEB documentation:

The first TFtoPL program was designed by Leo Guibas in the summer of 1978. Contributions by Frank Liang, Doug Wyatt, and Lyle Ramshaw also had a significant effect on the evolution of the present code. Extensions for an enhanced ligature mechanism were added by D.E. Knuth in 1989. Extensions to handle extended font metric files (``OFM'') were added by John Plaice in December 1995 and January 1996, resulting in the new program OFM2OPL.

and here's the lore drop: ofm2opl is based on the WEB source code for tftopl(1), although nowadays it is a link to omfonts, implemented entirely in C. glow-up fr fr. πŸ”₯

the primary authors of Omega were John Plaice and Yannis Haralambous. Omega (and Aleph) are now maintained as part of TeX Live.

this manual page was written by C.M. Connelly for the Debian GNU/Linux system. it is also now maintained as part of TeX Live. πŸ’–


okay that's the whole page, you're officially an ofm2opl scholar, go forth and convert. πŸ’…βœ¨

sign-off time, bestie: this one's from Web2C 2025, dated 8 March 2022, and she ate. πŸ‘‘πŸ¦‹