Personal tools

Websites/Taskforce/Proposals/Web Fonts

From MozillaWiki

Jump to: navigation, search

Web Fonts Proposal (Status: Draft)

Note: this may fit in to the brand toolkit project as part of codifying our font system.

Contents

Working Group

Ned Schwartz, John Slater, Sean Martell and David Boswell

Problem

FF Meta Sample

Mozilla branding uses the FontFont Meta font for logotype. However, FF Meta is a proprietary font with a closed license.

It is felt that it would serve Mozilla's goals best to search for a free and open alternative to FF Meta.

A free and open font becomes especially important when it comes to extending the Mozilla brand to it's web properties through the use of css3 @font-face embedding. FF Meta cannot be included in a Mozilla project without compromising Mozilla's goal of distributing only open-licensed code (where is this goal stated? -ned).

If you are interested, you can read a long-form discussion of the issue on the Drumbeat discussion group here: http://groups.google.com/group/mozilla.community.drumbeat/browse_thread/thread/93ead76b1e4c4993

Related Bugs

https://bugzilla.mozilla.org/show_bug.cgi?id=545012

This brings up a few questions:

  1. Should Meta be replaced completely in Mozilla branding, or are we just concerned about web typography?
  2. Do we want and/or need to have consistant typography across mozilla products and websites?
  3. How open do we need the licensing of our replacement font to be? Is simply being free as in beer good enough to allow code to be distributed? Or do we want a license that allows modification etc.

Solution

Overview

An ideal overall solution may be:

  1. Either adopt an existing open font or partner with a type studio to design a "mozilla font" that is free and open. Ideally the font would have both a serif and a sans and must be available to to community to hack on; for example by adding support for more languages etc.
  2. this font would be promoted as an official mozilla project on the projects page: http://www.mozilla.org/projects/ and mozilla would maintain a version controlled repo for it, bugzilla etc.
  3. This font would be hosted by mozilla (as well as third parties like Kenest.com etc.)
  4. include this font in mozilla product downloads (firefox, thunderbird ...)
  5. Use the font on Mozilla web sites.
  6. Rebrand with the new font (logos, etc)
  7. Use the rebrand as a big marketing opportunity to promote the use of open fonts, this font in particular, the WOFF format, the new mozilla branding as a further step away from proprietary and towards open source etc.

Where To Start

There are two basic approaches to selecting a font for mozilla; reach out to foundries we are interested in (proactive) or open up applications as a competition / RFP / open call (inclusive).

Regardless of the selection process, we need to decide: Adopt an existing font or Partner with a foundry and start from scratch?

    1. If we adopt: choose a font to adopt:
      1. What are the selection criteria for the font?
      2. How do we run the selection process?
      3. Vote?
    2. If we partner: choose a foundry to partner with:
      1. How do we choose partner/ what criteria?
      2. What arrangement do we make with them re:sharing and rights etc.
      3. What are the requirements for the new font?
      4. How much work do we need to get the font off the ground?

One solution is to find a font or set of fonts that Mozilla adopts and recommends for use in websites. There are a number of sources that list fonts that are available with varying degrees of free and/or open licenses.

Many of the free fonts are free for a reason; they are incomplete or are hard on the eyes.

Another Possibility would be to commission the design of an open font similar to Google's commissioning of Droid Sans.

Finally, a blend of the two would be to select a currently available free font and work with the foundry to flesh it out.

Font Hosting

It has be suggested that Mozilla could host one or more fonts for use by others. This would tie in with the typography solutions above. Upon selecting a font to be used in Mozilla websites, said font could be hosted to others in the mozilla community.

Fontue is an open source Font Server Developed for use at Kernest.com. The project is hosted on github.

We need to address issues related to hosting;

  • availability
  • browser compatibility
  • licensing
  • http/https
  • hotlinking vs. hosting locally
  • etc.

Use Cases

Already there are a few fonts that have been adopted in the Mozilla web universe:

Museo Sans

Museo Sans Sample

Museo is a great font, has serif, slab-serif and sans serif variations. Unfortunately the free members of the font are pretty limited: there is only one weight in each variant available, and the license is not very permissive.

http://new.myfonts.com/fonts/exljbris/museo-sans/ http://www.fontsquirrel.com/fonts/Museo-Sans

In use on:

Titillium

Titillium Sample

http://www.fontsquirrel.com/fonts/TitilliumText

In use on:

Droid Sans

Droid Sans Sample

Created for the Open Handset Alliance, Droid is a nice, quiet serif. It is very readable, but it doesn't have a huge amount of character, though it's open letterforms are attractive. The font is also limited in it's range, lacking italics in the sans-serif .

http://en.wikipedia.org/wiki/Droid_(font) http://www.fontsquirrel.com/fonts/Droid-Sans

In use on:

PT Sans

PT Sans Sample

PT Sans is not in use anywhere in Mozilla yet, but it is open and similar in feel (though inferior) to Meta; it is a humanist sans-serif with an inviting and fun character while maintaining clarity.

http://www.fontsquirrel.com/fonts/PT-Sans

Minutes from Web Task Force Meetings

September 23rd, 2010

There was interest in this topic and an agreement that the idea of creating a more consistent font style is worth working on. In terms of timing this looked like something to look at more seriously in 2011 due to scheduling issues for the rest of 2010, although we talked about things that could be done now for anyone interested in driving things forward.

One of the reasons for the delay is that a Mozilla and Firefox brand study is being done now and we should see the results of that before making decisions that could effect logos and sites. Another reason was that web projects for the end of the year are already under way that include the Meta font and we don't want to delay those because of this font discussion.

In the meantime though, we can do research on available open fonts that might serve some or all of our needs and we can also look into the technical issues with serving an open font in a way that could be re-used widely in the community. Neither of these things depends on what the final font choice will be so we aren't blocked by not knowing the answer to that now (for instance, we can set up a test font and change to a different font later for production use.)

Mozilla <3 Open Fonts

See Sean Martell's page about Mozilla <3 Open Fonts