OVF2OVP(1)

πŸ’– OVF2OVP(1) πŸ’–

okay bestie, welcome to ovf2ovp, section 1 of the manual pages, and no cap this one is a whole little converter fairy 🧚✨


✨ NAME ✨

ovf2ovp β€” convert virtual font file and associated font metrics to property-list format πŸŽ€


✨ SYNOPSIS ✨

ovf2ovp [options] ovfname[.ovf] [ofmname[.ofm] [ovpfile[.ovp]]]

✨ DESCRIPTION ✨

so basically ovf2ovp takes a virtual font (OVF) file, ovfname, and its companion font metric (OFM) file, ofmname, and translates them into a human-readable property-list format. it's giving translator, it's giving glow-up πŸ’…

by default the program writes to standard output, or you can send it to a file specified as ovpname instead.

and guess what β€” it's versatile, she works with TeX VF and TFM files too, producing TeX VPL files. obsessed. 🌸


✨ OPTIONS ✨

(Same as ofm2opl.) πŸ‘‘
  • -charcode-format=type β€” output character codes according to type, and type is either hex, octal or ascii. default is hex. if you say ascii, it uses ASCII for letters and digits and hex for everything else. πŸ¦‹
  • -char-format=stype β€” output character codes according to stype, which is either num or ascii. default is num; ascii behaves like in -charcode-format. (and yes, these two options are redundant, they both exist purely for historical compatibility β€” the way that legacy code just never leaves 😭)
  • -num-format=ntype β€” output numbers according to ntype, either hex or octal; default is hex. πŸ”’
  • -text-format=ttype β€” output coding scheme and family according to ttype, either mixed or upper case; default is mixed. ✨
  • -help β€” display a brief summary of syntax and options 🫢
  • -verbose β€” display progress reports πŸ“’
  • -version β€” output version information and exit πŸ‘‘

✨ FILES ✨

  • ovpfile β€” Omega Virtual Property List file πŸŽ€
  • ofmname β€” Omega Font Metric file πŸ’œ
  • ovfname β€” Omega Virtual Font file 🌈

✨ BUGS ✨

found a bug? email bug reports to <https://lists.tug.org/tex-k> (that's the mailing list). and lowkey it's a good idea to check whether the same bug is present in vftovp(1) first, fr fr. πŸ›

general discussion of Omega (and Aleph) can take place on the <http://lists.tug.org/omega> mailing list. come vibe with the community πŸ’¬


✨ SEE ALSO ✨

omega(1), aleph(1), ofm2opl(1), ovp2ovf(1), pltotf(1), tftopl(1), vftovp(1), vptovf(1)


✨ AUTHOR ✨

according to the WEB documentation, and I'm quoting:

VFtoVP is an extended version of the program TFtoPL, which is part of the standard TeXware library. The idea of a virtual font was inspired by the work of David R. Fuchs who designed a similar set of conventions in 1984 while developing a device driver for ArborText, Inc. He wrote a somewhat similar program called AMFtoXPL.

so therefore: ovf2ovp is based on the WEB source code for vftovp(1), although nowadays it's a link to omfonts, implemented entirely in C. main character energy from C, honestly πŸ’…

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 bestie, you're fully caught up, go convert some fonts πŸ’–

Web2C 2025 Β· 8 March 2022 β€” mwah, that's the source, version and date, signing off βœ¨πŸŽ€

πŸ“¦ where this page comes from