Much of the work that I did at P22 Type Foundry, where I broke in my type chops, was digitization of various designs. Have you done a digitization project like this before? So, how do you make a digital typeface, when you’ve got just physical artifacts to work with? It’s a long process, but Paul was happy to walk through it a bit. But usually the styles labeled ‘Bulletin’ feature the distinctive backslant.” On the Behance page for the digitization project, Paul noted the variously-named specimens he pulled from when piecing together sources for the design, including “Hamilton 117” (“Not very catchy,” he commented) and “Heber-Wells Bulletin Condensed.” Paul explained, “This is actually a bit of a tangled ball of yarn, with different foundries calling this design many different things and the ‘Bulletin’ name being applied to a whole host of related designs. “I’ve always had a soft spot for over-the-top ornate Victorian types, and this one definitely qualifies.”īulletin Script is one member of a larger typeface family, which was called “Bulletin” by some foundries, but not consistently. “It was the weirdest design in the set of candidates,” he explained. It was just one of several digitization candidates selected by Rich Kegler of P22 Type Foundry (who is heading up the effort), but it stood out to Paul. Some of Adobe Type’s own designers even got involved with the digitization work for these historic fonts - most recently Paul Hunt, who worked on Bulletin Script, № 2.īulletin Script, № 2 is a pretty psychedelic-looking font. For fonts loaded from a provider that does not support the current browser, the fontinactive event will be triggered.We’ve been having a lot of fun with fonts from Hamilton Wood Type Foundry lately, especially since we added so many new ones to our library last month. When finished, the active event will be triggered.įor fonts loaded from supported providers, the fontactive event will be triggered. If Web Font Loader determines that the current browser can support and at least one provider is able to serve fonts, the fonts from that provider will be loaded. When loading fonts from multiple providers, each provider may or may not support a given browser. If Web Font Loader determines that the current browser does not support the inactive event will be triggered. Web font providers can build on top of the basic Web Font Loader functionality to handle these special cases individually. The Web Font Loader is not designed to handle these cases and it defaults to believing what's in the user agent string. In this case a web font provider may decide to send WOFF fonts to the device because the real desktop Chrome supports it, while the mobile browser does not. This is especially noticeable on mobile browsers with a "Desktop" mode, which usually identify as Chrome on Linux. The user agent string may claim to support a web font format when it in fact does not. Browser SupportĮvery web browser has varying levels of support for fonts linked via Web Font Loader determines support for web fonts is using the browser's user agent string. If you're using Typekit, you should use their embed codes directly unless you also need to load web fonts from other providers on the same page. load ( įYI: Typekit's own JavaScript is built using the Web Font Loader library and already provides all of the same font event functionality.
0 kommentar(er)
