Webfonts FAQ

Q: Are you allowing CSS @fontface embedding with your fonts?

We are not allowing the conversion of our existing desktop fonts for CSS @fontface embedding. Font embedding with CSS has significantly different technical requirements for fonts than print and we are working on our most popular collections to prepare them to work to our high standards on screen. We are actively testing the first fonts and have some live solutions running. Our photolettering.com site uses Chalet for menus and body copy, a special version of PLINC West Behemoth for headlines and Swiss TwoTone display numerals.

Q: When will your fonts be available for CSS @fontface embedding?

We are actively working on versions of our fonts to be implemented with CSS @font-face embedding and are licensing select styles for enterprise-level implementations. Please contact us for more information.

Q: Can I use a third party tool to convert your fonts to webfont formats?

No. This is expressly prohibited in our End User License Agreement.

Q: Why not?
  • It is specifically prohibited in our End User License Agreement.
  • Third party tools often do not address the many technical concerns that will lead to inconsistent results across browsers and platforms.
  • We don’t want our fonts to be used with CSS @fontface web embedding until we think they are ready.
  • Third party tools are forced to auto-hint fonts. We spend far too much effort on our typefaces to allow subjective tools to make an automated aesthetic decision.
Q: Can I use static graphics with your fonts on the web?

Yes, we have never restricted this use. If the images are created on a human-operated workstation with properly licensed fonts and are static images, then no additional fee is required beyond our traditional licensing fees.