4 ms·
Very cool. I'm seeing a future where fonts are stored as a series of transformations rather than a bunch of bitmaps/glyphs/vectors. A client could have specific
by fnovd 9y ago
Very cool. I'm seeing a future where fonts are stored as a series of transformations rather than a bunch of bitmaps/glyphs/vectors. A client could have specifications for adapting any font to make it more readable for their particular set of eyes while letting the font maintain a unique "look".
- eyelidlessness 9y agoThe vast majority of fonts are not stored as bitmaps. Most font formats store glyphs as vectors with a variety of additional information for pixel hinting, ligatures and probably a handful of other details that I can't even think of off the top of my head.
- phlakaton 9y agoRight. They're even parameterized, in a sense, but pretty much the only parameter available on the client side is size, right? (Unless I misunderstand how boldface is applied these days.)
- eyelidlessness 9y agoI think Prototypo demonstrates the parameterization is possible, but typically (for now) font weights are distinct fonts. Sometimes boldness or italics can be naively faked, but it's usually not pretty.
- phlakaton 9y agoRight – I meant even traditional fonts could be seen as "parameterized" if you were squinting at them through a slightly foggy lens. :-)
- platinumrad 9y agoAside from, well, bitmap fonts, fonts aren't stored as bitmaps...