sub7 was a windows binary (client and server), but it’s possible there was an unofficial perl interface for it or something similar. the perl era definitely saw a lot of precursors to modern C2 dashboards
hetzner is really known for its german bandwidth prices, a change in the US is fairly insignificant IMO. for most applications you could just put a free CDN in front of the cheaper german service to reach the US
> what other font editors moreover to Glyph (mac only) have good support for advanced contextual alternates ?
any font editor that supports writing opentype feature code manually. glyphs for mac won’t really help you here: while glyphs will do its best to autogenerate as much opentype for you as it can, it doesn’t do much (anything?) for calt features
I would pronounce it tee-vix, because of the stock ticker symbol TVIX[0] which was a leveraged volatility ETN and very popular in its day. a little too popular - credit suisse delisted it a couple
months after the initial market crash brought on by the pandemic caused it to skyrocket
a variable font is a more generic term than a metafont. it’s a bit pedantic but while both have parameters, a metafont is usually parametrically generated based on its concept of a pen, whereas a variable font usually has different parameters that have been defined by manual bezier drawings. I don’t remember if metafont itself can produce a variable font but people have used metapost to go to SVG and then UFO (font source) from there
in metafont (the software) you can define a metafont (a font-valued function) in terms of bézier outlines as well as paths stroked with pens; the relevant metafont commands are 'fill' in the first case and 'draw' (rather than postscript's 'stroke') in the second. it doesn't have an equivalent of postscript's 'eofill'. chapter 13 of the metafontbook describes these commands
i don't know if there's a reasonable way to export any standard vector format from metafont; i think there originally wasn't
> has had any ability to tell me where, how often, or even whether a particular component is in use in the production UI
I built a dashboard to display this for the design system I work on at my day job to give product designers better visibility into production, using a library called react-scanner[0] and some logic related to the way our different product repos are structured / places where the component names are different between figma and react. there are probably other libraries for this sort of thing in different ecosystems, and you can always build your own with a parser as well.
all google fonts are OFL (the copyleft SIL open font license[0]) with the exception of some legacy fonts which are apache 2. they don’t publish fonts that aren’t OFL anymore