One of my major prompts for thinking about the essential qualities of open source has been the Google Web Fonts project, which claims to be a library of open-source fonts. I design type. I worked at Red Hat. I was intrigued by the concept. There’s no reason open-source fonts can’t exist. But on closer inspection, Google Web Fonts are not “open source” in any meaningful sense.
I wrote some previous comments (here and here) about Google Web Fonts as part of a discussion about Roboto, the new Android font. What follows is a more detailed criticism of Google Web Fonts, but it’s also a call for Google to do better. They can and they should.
How do I know they can? In the engineering arena, Google has shown itself to be a good citizen of the open-source world. For instance: Python. For seven years, Google employed Python’s creator and benevolent dictator, Guido van Rossum. According to Guido, he got “to spend half [his] time on Python, no strings attached[.]” Google has adopted Python as its “main scripting language.” Google has released Python source code and libraries. Beyond Python, Google maintains a whole blog devoted to its open-source activites. Even the Google Web Fonts team has released open-source code for reading and editing fonts.
But what you won’t find on Google’s open-source blog, nor on its Open Source Programs website, is any mention of the Google Web Fonts themselves. This is odd, because according to Google, “All of the fonts are Open Source.” Really? The omission suggests that Google might have doubts whether these fonts qualify as open source.
I’m convinced that they don’t. To make the case, I’ll step through my seven essential qualities of open source (including the dilution–reality dichotomy introduced in that article). I’ll explain how Google Web Fonts falls short, and what Google could do to improve the program.
Essential quality #1
Dilution: Open source arises from a spirit of freedom and cooperation.
Reality: Open source arises from a spirit of capitalist competition.
It’s no coincidence that Google launched its webfont project in May 2010, the same period that other competing services (like Typekit and Webtype) were also getting off the ground. It’s also no coincidence that this effort has emerged during Google’s campaign to become more platform-oriented rather than application-oriented, building out Android, Chrome OS, and Google Docs. The Droid and Roboto font projects are the clearest examples of platform-oriented fonts.
So let’s agree that Google is pursuing Google Web Fonts primarily because it’s in Google’s competitive interests to do so. It’s not altruism. And these fonts are “free” only in the trivial sense that Google does not charge us to use them. But Google always finds other ways to convert our attention into revenue, either directly (selling ads) or indirectly (distributing open-source code). These businesses are lucrative for Google because our collective attention is economically valuable. That’s why Google is a $200 billion company.
My complaint with the Google Web Fonts project isn’t that Google is benefiting from it. There’s nothing wrong with making money from open source. Many companies do. It’s that Google is trying to pretend otherwise by flying the flag of freedom and sharing:
“We believe that there should not be any barriers to making great websites… you are free to share your favorites with friends and colleagues … If you design fonts and would like to contribute your own designs, please get in touch…”
This is disingenuous. Google does not care about “barriers to making great websites.” Google cares about Google. It’s also contrary to Google’s usual policy of not being cagey about how it makes its money. When Google puts an ad on a page, there’s no guile about what it is or why it’s there. Why is Google playing its cards close to the vest in this instance? Which brings us to the next point:
Essential quality #2
Dilution: Open-source developers work for free.
Reality: Open-source developers are paid.
The idea that open-source contributors work for free is one of the most persistent and insidious myths of open source. Insidious because it’s the preferred tool of companies who want to harvest the benefits of open source without assuming its burdens.
Here, it’s not in Google’s interest to reveal the boring reality — Google benefits from Google Web Fonts — because it would dampen the enthusiasm of the designers who contribute fonts for little to no money.
In the design world, there’s a well-known swindle where a prestigious but stingy client says “I wish I could pay you, but I don’t have the budget. How about you let me use your work for free? I know it’ll be great exposure for you, and lead to paying work.” In truth, it’s not, and it won’t. Designer Jessica Hische aptly calls this “the most toxic line of bullshit anyone will ever feed you.” Why? Because it’s just good-natured grifting, an exploitation of the weaker by the stronger. Nevertheless, it works, because there will always be designers hungry enough to believe that they don’t have other choices.
Google Web Fonts uses a variation of this toxic line as part of its pitch to potential open-source font contributors:
“We are working with designers around the world to publish quality typeface designs that are made for the web. If you design fonts and would like to contribute your own designs, please get in touch. Fonts in the directory can become very popular and seen by millions of people every day.”
Google is using the lure of exposure to “millions of people” as an inducement to get designers to contribute their time and their work for less than its market value, all for the pleasure of being an open-source contributor.
To be fair, over the past year, Google has been making more of an effort to pay designers. One Google Web Fonts contractor told me that they were offering $500‑3000 per font. Let’s suppose Google pays you in the middle of that range ($1750) for each style in a four-style font family, or $7000 total. Let’s also suppose you spent three months on that project. Do you think that’s comparable to what a web designer employed by Google would get paid, including benefits, health care, stock options, etc. in the same three-month period? Clearly not.
How can Google do better? One model is to pay market rates for type-design services and then release the results under an open license. This was the model for the Droid fonts, made by Monotype Imaging. It would be an improvement, but not especially open-source in spirit.
The better option would be for Google to embrace the open-source model more wholeheartedly. Google doesn’t pay community engineers to work on open-source code. So Google also shouldn’t pay community type designers to work on open-source fonts. Instead, Google should provide those type designers the other benefits of working on an open-source project. (Keep reading.)
Essential quality #3
Dilution: Open source makes things free.
Reality: Open source redefines what is valuable.
In the open-source model, the point of making software code free is not to destroy the marketplace for software, but rather to shift the value elsewhere. Making one thing free without making something else more valuable misses the point.
Google has likewise missed the point by releasing hundreds of fonts for free without creating corresponding value elsewhere. In that regard, Google Web Fonts is not part of the lineage of open-source projects, but rather file-sharing projects like 1001 Free Fonts, which are guided by the principle “Here’s a bunch of useless crap that you’ll like because it’s free.”
You might counter by pointing out that the Google Web Fonts team has created new value by releasing open-source code for working with webfonts. True, but I consider the code-writing part of Google Web Fonts to be distinct from the font-creation part. Google has a good handle on how to work on open-source software. What Google is missing is a similar rationale for fonts.
How can Google do better? By putting forward a coherent concept of how Google Web Fonts can redefine value in the font market. The world already has plenty of useless free fonts. Google Web Fonts is blazing no trails there.
Google has multiple options. I think that Google Web Fonts could be an interesting training opportunity for aspiring type designers who can’t drop everything and move to Berlin or New York (or other urban center) to learn the trade. In this way, it would be similar to how open-source software projects provide opportunities for engineers without a strong résumé to learn and contribute. But the value of this mechanism depends entirely on the next point:
Essential quality #4
Dilution: Open source has no barriers to participation.
Reality: Open source relies on meritocracies.
I alluded to it above, but this is the moment to fully confront the unavoidable truth: measured by professional standards, the average Google Web Font is just awful. Some are better than others, but nearly all fall prey to at least one fatal flaw of being ugly, incomplete, poorly drawn, poorly spaced, amateurish, or just unusable. And I don’t say that to criticize the designers themselves. They’re enthusiastic about type design. But that enthusiasm should be channeled into improving their skills and making better fonts. Right now, it’s not. And Google isn’t helping.
If you think it’s unfair to compare Google Web Fonts to professional fonts, sorry, but that’s the open-source way. (See also Essential Quality #1.) The open-source option is only relevant if it can compete with the quality of the proprietary version. Does Google release tons of low-quality open-source code into the world? No. It lives up to professional open-source standards. Google should adopt analogous standards for fonts.
How can Google do better? This one’s easy: fewer fonts, higher quality. The need for new fonts is never in doubt. Time passes. Technology evolves. Requirements change. In the last generation, companies like Apple and Microsoft invested large sums in making the system fonts that millions of people have relied on for 20 years. Google has the opportunity to step into that role, if it chooses.
But making quality fonts requires quality designers. Open source does not mean “open to all.” It means “open to all who can work to the necessary standard.” If Google wants quality, Google Web Fonts cannot remain open to anyone who wants to give a font away for free.
Essential quality #5
Dilution: Open source is democratic.
Reality: Open source relies on benevolent dictators.
This one’s also easy: assuming that Google developed fewer fonts, each project should be led by an experienced, respected, professional type designer. This would be analogous to open-source software, where projects are led by experienced, respected, professional software engineers. Google should pay these professional type designers market rates to assume these roles. They would become the arbiters of which contributions get included and which don’t.
Three results: 1) Google would get professional-quality fonts at a lower cost than proprietary development. 2) Community type designers would get to work with professional type designers (which is the best way of improving skills). 3) Google would be releasing genuine open-source assets into the world, that would be good enough to inspire more development. For instance, the freely available font Charter — designed by the esteemed Matthew Carter in 1987 — became the basis of Charis SIL. Have any current Google Web Fonts been similarly adapted?
“But under this scheme, far fewer designers will have their contributions used.” Yes. That’s the point. Benevolent dictators get to pick the worthiest contributions. Open source is not open-mic night. Those who want to release a font for free will always have plenty of options. It’s not true that anyone is entitled to participate in an open-source project. If you disagree, please get me Guido van Rossum on the phone, because I want him to add Klingon commands to the core syntax of Python. And an ASCII unicorn to every source file.
Essential quality #6
Dilution: An open-source project can have one developer.
Reality: An open-source project requires multiple developers.
Most Google Web Fonts are the work of one to three designers, working in isolation from other designers. Maybe Google does some rudimentary quality control — it’s hard to tell from the results. But in most cases, the font is done when the designer says it’s done. The font does not have to meet any external standards.
With multiple designers working under a benevolent dictator, there would be a competition of design ideas. Type designers who were lazy or careless would quickly find that there was no room for their work. They would either improve their work, thereby becoming better designers, or retreat. Either way, the project would benefit.
Essential quality #7
Dilution: A software project can be open-sourced at any time.
Reality: Open source is part of the project’s DNA or it’s not.
In theory, there’s no reason open-source fonts can’t exist, and can’t be good. I’ll assume that Google sincerely wants to make fonts that have open source in their DNA, and not just “Another 1001 Free Fonts.”
But if that’s the case, Google has to change its approach. I said before that “Google has a great engineering culture, a weak design culture, and no discernible taste.” I stand by that. To get different results, Google will need to approach open-source fonts in a way that plays to its strengths (engineering) and avoids its weaknesses (design and taste). Focusing on a smaller number of fonts and hiring benevolent dictators from the professional type-design industry would be good first steps. Even Microsoft was able to overcome its taste deficits to make Verdana, which is now in the Museum of Modern Art.
More broadly, Google should consider that its interests as a participant in the font world are parallel to its interests in the software world. Regardless of whether your project is open or proprietary, the results depend on the talent of the people building it. Developing the talent pool always pays dividends. But that can’t happen by merely making fonts free. It requires a more thorough and thoughtful approach. Google is possibly capable of that.
It’s also possible that Google, with its cultural bias toward engineering, simply doesn’t acknowledge that type-design skill exists and has value. If that’s so, Google Web Fonts will remain the Costco of typography: always getting bigger, never getting better. If that ends up being in Google’s best interests, fine. But please, Google — don’t call it open source. You know better. So do we.
[A few more words about how quality begets quality in creative endeavors, and how for Google, typography is part of an advertising economy, not a creator economy.]

The fonts are distributed under the SIL Open Font License, recognised by the Open Source Initiative as an ‘open source’ license.
In my personal opinion, I and the Web Fonts team at Google hasn’t encouraged public participation in the fonts it has commissioned, but the license allows anyone to participate if they wish.
As a blog post on the OSI website put it, “a license is insufficient to make something actually open source. The license just helps pass the sniff test.” The SIL Open Font License is the beginning of the story, not the end.
OSI does itself a bit of a disservice to have an “Open Source Definition” that focuses largely on software license terms to the exclusion of what we might call the cultural norms of open source. But if you read the OSI’s mission statement, you get a fuller picture:
“Open source is a development method for software that harnesses the power of distributed peer review and transparency of process. The promise of open source is better quality, higher reliability, more flexibility, lower cost, and an end to predatory vendor lock-in.”
My seven essential qualities are not intended to exactly model the OSI values, but you can see the connections.
Even if we restrict ourselves to the OSI version, the fact that Google “hasn’t encouraged public participation in the fonts” means that Google has not sought out “distributed peer review.” Nor has Google sought to establish Google Web Fonts as a “better quality” alternative to proprietary fonts. As for “predatory vendor lock-in,” while Google doesn’t make it especially difficult to download the fonts, it strongly encourages users to access them through Google’s servers rather than download. It’s hard for Google to make the case that it lives up to the OSI values.
In my oppinion you have good points, but you are losing some ones:
- Many fonts in GWF were a propietary work by prestigious designers and were released, some of them prize-winners. If all the fonts are «ugly, amateurish, etc» it means that also propietary fonts are ugly, amateurish and the recognition of their designers is absolute crap.
I think this is a generalization, there is great work there. And the high quality foundries, famous designers and distributors have lot of crap in their catalog.
- If all the work is amateurish, incomplete and awful maybe the $1750 average is a great price for an amateurish designer. But many well known and successfull typographers are there and I don’t think they are just destroying their business for coins. I’m pretty sure they are getting a reasonable value and something that works for their business model. Or they are stupid, which is a possibility.
- «who can’t drop everything and move to Berlin or New York to learn the trade». Well, there is great typeface designers with great work and they didn’t move to Europe or USA. There is great schools in Asia, South America and Australia and actually many people doesn’t need to move to the Center of the Universe.
Andres sets a petty low bar for “great typeface designers.” I think there are fewer than 20 working today, and none of them is represented in GWF.
MB, I think you’ve summed it up in a nutshell. Impressive analysis!
@David
You can find fonts by Type-Together and AlePaul on the GWF among other great type designers as Pablo Cosgaya, Eduardo Tunni, Dario Muhafara, Alejandro Lo Celso, Juan Pablo del Peral (recent Letter2 winner) and many others.
@MB
Comparing it to 1001 free font is totally unfair.
Here you have a list of great quality typefaces on GWF that deserves much more than that:
– Passion One
– Crete Round
– Almendra
– Overlock
– Bubblegum
– Gentium
– Abril FatFace
– Mate
– Bree Serif
– Galdeano
– Bitter
– Petrona
– Andada
– Rosario
– Chivo
Just to name a few…
Maybe you missed the latest additions, I recommend you to check again.
Also, if you check the repository, you will find a nice surprise there, soon to be released.
Regarding the collaborative aspect, you have to keep in mind that collaborating on “Design” stuff it’s not as easy as collaborating on “Programing” code. That’s why you don’t see as many collaborative design as you see collaborative programming.
There is no easy way to merge design ideas as there are tools to merge code, unit testing, etc.
So, collaboration is carried on as much as possible. For example, on my own fonts, I’ve collaborated with people who have made corrections, extended the char-set, added Cyrillics, hand-hinting, etc.
Raph Levien is working on a collaborative type design tool, witch he showed at the latest ATypI conference. I hope this new tools will improve the collaborative aspect of type design when released.
Anyway.. any suggestions on how to improve collaborations is always welcome.
Matthew raises some good issues here. I haven’t looked at GWF in a few months, but the last time I did, my conclusion was the same as his — the quality just is not there.
I have some experience in this area. I headed a team at Microsoft which produced some of the best onscreen fonts in the world, including Matthew Carter’s Verdana and Georgia. We also produced the excellent ClearType fonts, and Meiryo (intended to create technology for screen-readable complex Asian glyphsets, Meiryo began life with the internal code-name of Verdana-J. Matthew Carter was again brought in to collaborate, especially on the harmonization of Romanji and Kanji).
The recipe for producing great fonts was the same in every case. Define the projects well, up front. Work with great external designers. Pay them fairly for the work they do.
Have your own great internal typographic experts who can oversee and manage the projects from start to finish.
Define standards for fonts: character sets, etc.
Recognize that creation of great fonts does not end with either the design or the creation of the outlines, but involves many other factors including testing, quality control, etc.
There’s no reason why some of this work could not be done as Open Source. But, as MB says, there’s a need for benevolent dictatorship in at least some areas. Design is not democratic; art is not a committee pursuit.
Viewing its fonts so far, GWF strikes me as just too casual and haphazard, and seems to rely on what fonts people wish to contribute, rather than any systematic approach.
Producing great fonts is a very expensive business. Microsoft, for all its faults, recognized this, and spent huge sums of money over more than 20 years on fonts for Windows, Office and the Web. It had perhaps 20 internal employees working full-time on font projects, in addition to outside designers and consultants.
If Google is really serious about Web Fonts, it needs do the same; bring a new professionalism to the project, and hire its own experts to run it. And it needs to recognize that doing it properly will take time and money. Despite the protests of some of the commenters, there really are not that many great type designers out there who can produce world-class fonts.
There are great type designers.
And there are good type designers.
In a nutshell, the biggest issue is a lack of strong type direction. Even a group of the best type designers can flounder without a good type director to identify what kinds of fonts are needed (or not) and how to go about making them.
Think of people like Chauncey Griffith, Morris Fuller Benton, Robert Hunter Middleton, Mike Parker, etc … They oversaw entire departments of people working on collaborative type development projects before digital type even existed.
With modern font formats (UFO) and code repositories, there’s no reason type design can’t easily be a collaborative effort today too.
I should be clear that my comments here reflect my own personal opinion and not the views of any of my consultancy clients, including Google Inc. So when I earlier said that ‘Google hasn’t encouraged public participation’ then I mis-spoke, and really I mean that I personally haven’t focused on encouraging the kind of public participation that is common to libre culture projects.
In working to cultivate a libre type culture over the last few years, I have, gently and in passing, encouraged designers commissioned by Google Web Fonts have made some small steps to work in this way — placing the font files github for example, or running a font project blog actively encouraging public participation — but these efforts by designers haven’t led to much interest.
Vernon Adams is one of the most active type designers working on web font commissions for GWF, and he is publishing all work in progress in a blog and also publishes all his working files in a Google Code project. I hope Vern can comment on how many people have contacted him in the last 2 years about contributing or collaborating.
The Kickstarter projects that Google Web Fonts supported have also invited participation from backers, which is something perhaps Pablo can comment on. My understanding is that participation has been muted there too, despite that people have paid from their own pocket to fund the designer.
There were some lengthy discussions on Typophile when libre fonts started growing, about 6–7 years ago, and the idea of public participation in type design has been ridiculed; however, the vision of participation built into the Open Font License’s Reserved Font Name feature has been shared and turned into a very popular workflow by GitHub.
While Nick mentions the UFO (or SFDir) formats and project hosting that solve part of the problem, the lack of equivalent tools for managing revisions in text for fonts don’t exist — and as Pablo says, Raph Levien has been making some explorations in that area.
So there appears to now be a gradual acceptance that public participation in type is realistic, and its nice for me to see people calling for it to be done better. I will do what I can
Regarding the ‘sniff test’ you mention, there is a Google Code project ‘googlefontdirectory’, where the source files for the fonts are published; this is linked to quite prominently from the download dialog of the main GWF website; and the public do regularly report issues in the issue tracker there. So I think the GWF project clearly passes the sniff test.
Also, last month I started a small project to do peer review of fonts — http://typereview.wordpress.com/ — and if anyone is interested in doing similar review consultancy, I hope they’ll speak to me directly.
I was looking forward to reading this. However at the risk of exposing myself as stupid on the super highway can you explain the meaning of the “Dilution” and “Reality” sections in each “Essential Quality”? I am lost.
[I added a note that the dilution–reality comparison comes from my earlier article about the seven essential qualities of open source. — MB]
I just checked the review blog Dave mentioned. There is a typeface in progress there called “News Cycle”. The designer claims that it is “based” on News Gothic. From what I can see in the specimen, “based on” is a euphemism for a straight-forward copy, aka Rip-off. Does anybody chez Google look at the sources of these “free” fonts? If you use existing outlines, making a free font doesn’t need much work. I wonder whether the publishers of the original agreed to their intellectual property being made Open Source without their consent.
News Gothic was first published in 1908 and is therefore in the public domain. News Cycle is a straight forward copy, and entirely legitimate — just the same as Linotype and Benton Sans
The digital outlines are not in the public domain. And I would bet that “based on” in this case means that the designer used someone else’s outline.
I cannot believe that you would mention Benton Sans here. That is a different typeface altogether. Clearly inspired by News Gothic and named for its designer, but completely redrawn. As is the new Linotype version, albeit much closer to the original. Linotype based this on their own version which they are entitled to use.
So there is many great typeface designers as great astronauts in the world: twenty. Wow!
Between TDC, Letter 2 and Tipos Latinos we had about 100 recognized great designs.
Some of these designs and his designers are in GWF or will do soon.
I agree maybe most of the fonts there are not high quality. But it is not true to say:
- All in GWF is low-quality.
– Comissioned fonts for GWF are under paid.
– A good typographer has to study in Europe.
«There really are not that many great type designers out there who can produce world-class fonts». There are hundreds! But only a few of them will have the budget to do world-class fonts.
Typography is not quantum physics.
PS: The 100 designers were recognized only in the last year.
@Erik,
I think that as the audio is in Spanish, you may have misunderstood the video.
What you see there, is not a type in-progress using proprietary digital outlines as a base font.
It’s a review session by Angelica Diaz, fixing errors and improving News Cycle outlines by Nathan Willis.
If News Cycle where based on proprietary outlines, then there would be nothing to correct.
The fact that corrections where needed, proves to some extend that it was a new digitization.
If News Cycle where based on proprietary outlines, then there would be nothing to correct.
The fact that corrections where needed, proves to some extend that it was a new digitization
Oh no, it does not. It could simply mean that someone alters someone else’s outlines, but not well enough. Or not far enough away from the original.
BTW: my Spanish is good enough to get that.
News Cycle is absolutely not made using any other outlines. The scans from the ATF catalog are published along with the source files by the designer at https://launchpad.net/newscycle/with-samples — another example of the designer commissioned by GWF who took up my suggestion to make the font in a way that invites the public to participate.
Glad to hear that, Dave. That is a good way to get a new feel out of an old prototype.
Just looked at News thingy: it needs work. Apart from some stray points and a few wobbly curves, characters like lc e are egg-shaped, which is not what Benton had in mind when he designed News Gothic.
@MB:
1. Typography as an industry wouldn’t be able to pass OSI’s ‘patch test.’ That example you link to on the OSI blog is so dependant on the candidate project being some sort of code based application.
2. Not all the fonts are created at Google. They’re licensed. Or comissioned. So it’s up to the type designer to seek distributed peer review.
3. A recommendation to load files from a CDN vs locally downloaded makes them anti open source? It’s well documented that loading assets from a CDN is beneficial to the end users. If a copy of a Google Web Font is already loaded into a user’s browser cache then it won’t need to download that font again if another site uses it. This is why typekit, fontdeck, et al host font files without offering downloads. Google offers downloads because some sites (like internal intranets) can’t use hosted files. Typekit and the like don’t have any support for enterprise.
Agree that generally “Google has a great engineering culture, a weak design culture, and no discernible taste.”
However, two recent projects lead me to believe things are changing for the better:
http://www.thinkwithgoogle.com/quarterly/speed/note.html
http://www.googlezeitgeist.com/en/
I really enjoyed this Matthew. I’m glad to see you in the mix. One small note. I think you mean “delusion”, rather than “dilution”.
On reflection, I’ve done Alexei Vanyashin (Cyreal) and Eben Sorkin a disservice by not mentioning them as examples of some the stuff that Matt is proposing that just isn’t very publicised. Each has a team of designers distributed around the world who they work with closely with to increase the quality of the work delivered to Google — doing exactly this kind of ‘benevolent dictator’ coaching. The evidence for this is in the FONTLOG files in the font source directories.
Thanks to this post, I’ve heard from some of the professional type-design industry folks who have offered to step into this ‘benevolent dictator’ role for any less experienced designers who want such help and are working independently
Google isn’t curating these fonts; it’s acting as a repository to make them available to websites. In other words, it’s acting basically like GitHub or Bitbucket. Both of those sites host plenty of crap open-source projects. Saying GWF needs a “benevolent dictator” is misunderstanding what it is.
I wanted to thank you for talking about “grifting.” As a musician, this happens all the time in my business, and the result is that pay goes down for everybody, and a lot of people get taken advantage of. When many people will work for free, it causes those wanting the service to think it isn’t worth much…
What thrills me more is, the fact that most of the type designers doesn’t accept the fact that, you should work and get paid once, and not working as a king getting lifetime tributes.
Nobody pays me for every design I do. If Google pays you to design an open source font I do believe it’s ok. Why shouldn’t? Is the price the main problem? Solution: ask for more money.
Google isn’t curating these fonts; it’s acting as a repository to make them available to websites. In other words, it’s acting basically like GitHub or Bitbucket.
But it surely looks like Google is offering those fonts, as opposed to e.g. Google Image Search, where it’s obvious that you get results from third parties with no involvement by Google.
Well, are the Google web fonts curated? Has any submitted font so far been declined for whatever reasons?
Perhaps Google doesn’t need to care if the fonts are of any particular quality as long as people use them. The tricky thing is, that even if people put these fonts in their website and feel good about having been given cool fonts from Google for free, they may be doing a disservice to their readers and not even notice it – when fonts fail on a particular system for technical or design reasons, deterring the reader. Which is the opposite of taking responsibility for a better web, something that I’d say would fit Google (»With great power comes great responsibility« – to quote Spider-man’s uncle), but probably isn’t necessary for their business interests.
“Open source redefines what is valuable.”
Actually, the purpose of all of Google’s “open source” projects is to, “destroy the marketplace”. In a marketplace where there is no value, it’s harder for a competitor to thrive, and easier for one with deep pockets to capture eyeballs for ads. This is the basic strategy in all Google’s projects over the last 10 years.
There’s a deep confusion at the heart of this piece. It’s summed up by this quote:
“And these fonts are “free” only in the trivial sense that Google does not charge us to use them.”
In reality these fonts are “free” in the rather important sense that the people who created them (which in almost every case was not Google) have released them under a licence which allows (amongst other things) for Google to then distribute them, and you to use them in commercial works, bundle them with Open Source software and so on. What most people would consider generally consider to be “open source” in fact. I realise that you have your own idiosyncratic and somewhat subjective definition of that term but you don’t really make clear whether you believe that it is generally accepted by the wider community (in my opinion it’s clearly not, though whether any one definition would be acccepted is another question).
The rest about type appears to be mostly snobbery, no different from early criticisms of Wikipedia or Open Source software or digital cameras or digital music by snobs of a different persuasion.
Why you are blaming a single company for these early teething issues is not clear though. You mention Red Hat, who’ve similarly done good work in getting fonts to display better on the desktop and funded font creation. Why are they not being held solely responsible for the state of currently available Open Fonts instead of Google? Both have contributed great work to build the foundations for the future, surely therefore they should both be criticized if we have not yet reached perfection?
Can somebody tell Andy that no one who reads Matthew Butterick thinks expertise is mere “snobbery”?
Some people really do know more than you and have better taste.
@Joe,
I’m not disputing expertise or even taste. I’m saying that things can and do improve from humble beginnings. My first digital camera was frankly terrible, the pictures were barely recognizable, it didn’t stop me from seeing the potential all those years ago and even then it had utility for certain use cases. Similarly my old phone had a terrible camera, that still worked as an optical sensor that could read barcodes, sense light levels and take my heartbeat.
But some people are too close to the issue and harp on about quality to such an extent that you think they’d be able to recognize the obvious quality increases over time if they’re paying attention and are so attuned to subtlety, even if that level remains, for the time being, below some personal limit that matters for them. But then you realise that they’re snobs and will always believe the new way to inherently inferior.
Google isn’t curating these fonts; it’s acting as a repository
This is clearly not true, since Google has an agent out in the world soliciting fonts from type designers and offering money for them. So Google is curating in the most important way possible: with its wallet.
you have your own idiosyncratic and somewhat subjective definition of [open source] but you don’t really make clear whether you believe that it is generally accepted by the wider community
As I said in my earlier piece about the seven essential qualities of open source, nobody owns the term “open source.” Not me, not you. If you don’t like the essential qualities I propose, you’re welcome to adopt your own. What I caution against is adopting a definition of open source that boils down to “file sharing,” i.e. releasing something under an open license. I think this is a dilutive interpretation, and that “open source” connotes more. As I said in my earlier comment, the Open Source Initiative also thinks it connotes more. As I argue above, Google also thinks it connotes more (based on their conduct in the open-source software arena). This last point is important — part of what I’m arguing is that Google isn’t living up to its own norms of open source.
Therefore, to reach the idea that Google Web Fonts are open source, you not only have dismiss my view as “subjective” and “idiosyncratic,” you also have to dismiss the OSI’s view, as well as Google’s conduct as an open-source participant. Which you are welcome to do, but at that point the burden of proof is on you to explain why.
The rest about type appears to be mostly snobbery
Snobbery is a judgment of something based on its source rather than its inherent qualities, e.g., “These french fries can’t be good because they come from McDonald’s.” I’m not criticizing these fonts because they come from Google, nor because they’re freely distributed, nor because many of them are made by inexperienced designers. I’m not even really criticizing them for being awful per se, because we could look into many proprietary type libraries and find awful fonts too. Rather, their awfulness — which is a judgment based on their inherent qualities — is evidence that Google is not living up to a key open-source norm, namely competitive quality.
Comparing fonts to early-stage digital cameras or open-source software is misleading. There was a time when Google Web Fonts would’ve been considered state-of-the-art. That time was 1991. The “humble beginnings” of digital type design are long behind us. The way we acknowledge progress is by raising the bar. If you still disagree, maybe I can interest you in buying my Apple Quicktake 100. Excellent condition, original box and manuals.
Alegreya, Letter2 winner.. just added.
Alegreya is ugly and amateurish, just as everything there. Only 20 guys in the world can make great things.
For clarity, Google’s “agent” handing out cash for fonts (“TOO MANY FONTS? NOT ENOUGH CASH?”) is whom, exactly?
I cannot believe you actually mean this. We are not talking about a small sweatshop that is just learning about digital type. This is Google who could buy the whole type industry out of petty cash! And, as Matthew has pointed out, the beginnings of digital type are 20 years and more behind us. For Google of all people to claim innocence is absurd, even cynical.
Not sure how this fits into the larger debate, but there is at least one project that aims to do open-source typography in a curated fashion: http://www.theleagueofmoveabletype.com/ (I’m probably not qualified to say whether they’ve succeeded, but their one page of samples did make me download the whole thing. GWF inspires no such urge.)
If the humble beginnings of digital type are behind us why is it still a novelty for a web site to use any font not one of a handful provided by default by Microsoft? Or use the font-weight: 100–900 property to its full potential? Or use ligatures? Or real small caps? Or lining or tabular numbers? Or typeset maths? Or use decent justification and hyphenation? How many people are using devices or software that require elaborate and expensive hand-hinting for fonts to display properly? We’re clearly still in the wild west of web fonts.
As I said, it is getting better. I can see the improvements that have happened recently and are coming down the track. And open source software and/or Google is leading the charge on many of these items since they both want the web to be better.
Are people approaching this as “Google should be providing amazing, free, open source digital typefaces for my use but I don’t particularly care about using type well on the web” or am I the one missing something?
We’re clearly still in the wild west of web fonts … or am I the one missing something?
Yes, you are missing something: namely, the critical distinction between fonts and the technology that displays fonts. Type designers have a lot of control over the former, but none over the latter. Ligatures, small caps, kerning, lining and tabular figures, etc. have been available in fonts for years. What’s been missing is the browser support, which has only arrived recently. If you were a user of, say, Adobe InDesign, all of this would be old hat.
I have no complaint with the technology side of Google Web Fonts (as I note under point #3 in the essay). In fact, I consider it the most valuable part of the project. If Google Web Fonts allowed me to host my own webfonts from their servers using their technology, that’s a service I’d probably use. If Google licensed and integrated the excellent Font Squirrel @font-face generator, that’s a service I’d definitely use.
Matt, curious to hear what your examples of quality web fonts are
As a typography enthusiast, I’d almost agree. But as a realist, I can’t.
Google Web Fonts doesn’t aim to make high-quality typography free, it simply gives the ordinary person the ability to experiment with type online. The same kinds of people who would previously use and abuse Comic Sans. There is no better way to raise the profile of typography than to give people stuff to play with.
Does it suck that the fonts are often of lower quality, that the kerning is off, that the italic is generated? Sure. But it’ll be a tiny bit more inspired than yet another Times New Roman or Verdana. And after a while, they’ll probably figure out themselves that some things look weird and others look good.
Text doesn’t become beautiful just by using the right font anyhow, it takes a lot more than that. If you care about that, you’ll either look for the few free GWT gems, invest in commercial fonts, or pay a designer to do it for you.
[…] the way, this post was inspired by Matthew Butterick’s own critical look at Google Web Fonts. Matthew makes some good points, but overall I still think Google Webfonts is a great […]
I’m somewhat wary of contributing to this essay, as i’m aware there is a wide gulf between my own practices & interests in type & type design and the practices and interests of others here; a gulf too wide to make for dialogue. For example, I don’t believe in ‘great design’, or great ‘designers’, and i don’t believe in proprietry production methods, instead i see most value in the ways in which the ‘fascis’ of ‘design’ can be re-shaped, subverted, freed, and re-used. In other words, we are not going to agree on design matters
However, on the practical side, i think it’s worth noting a few things.
1. In my memory, people have talked a lot, for a long time, about serving type over the net, but not really done that much. The situation is better now that, in the last few years, some people have, at least, started doing ‘something’.
2. A lot of the google fonts get used a lot. Aka more than fonts from other webfont directories. They clearly serve purpose & function.
3. A lot of the google fonts (and the server-side itself) are ongoing, being improved, still being shaped, but in the open. This is apparently not a problem for users (see point 2).
4. Users actively and helpfully feed back. This can be put, in my experience, into three categories; a. “thanks, give me more”, b. “i notice something wrong, please fix it”, c. “something was wrong, i fixed it, file attached”.
As far as i’m concerned that’s a functioning, positively evolving system. How is your system doing?
As for the general idea of the font’s not being ‘open source’; it’s an interesting intellectual exercise (i guess), but behond that i don’t see where the magic is in claiming these ‘open’ fonts are ‘closed’. Where’s the trick meant to be?
Vernon, if you “don’t believe in ‘great design’,” then you’re not really doing design, at least as most designers understand that term. You’re doing some kind of conceptual performance art that takes design as its subject. If that’s interesting to you, great. I’m not here to talk you out of it.
As I said in a previous comment, the point of this essay is not to argue what Google should or should not do. Nor is the point to argue that these fonts serve no purpose — indeed, I’ve already agreed that they “fill a practical need”. The point is simply that Google has applied the term “open source” to fonts in a way that’s inconsistent with how that term is typically used, including how Google has typically used it. If Google renamed it “Google’s Giant Pile of Free Fonts,” I’d have no complaint.
But if it were so named, I think many fewer type designers would participate. In my view, Google describes these fonts as open source to add an ethical veneer to the project that it hasn’t earned, and thereby induce participation from more type designers. This is good for Google. It’s not so good for type designers. (This will the topic of a separate essay.)
The defenders of Google Web Fonts have so far failed to explain one critical fact: that Google continues to push out new fonts by the dozen, instead of consolidating effort into fewer families to make them better. We’re told that the mantra of open-source font development is “release early, release often.” But “release often” is a synonym for “revise and improve.” In practice, Google has put far more emphasis on the “release early” part.
Mathew, i wonder if your are approaching this too much from the view that ‘Google Webfonts’ is some homogenous, static, whole. I suggest it’s not good orienteering. Think ‘crowd’ rather than ‘law court’. Some of the larger type foundries have created webfont directories more on the model you seem to prefer, so just use those services if you are approaching this as a user. If your interest in google fonts is more intelectual, then we are talking of such different models that they are just not comparable, hence you having to resort to gymnastics to re-imagine font files freely and widely available under opensource licenses as not really open source. And i don’t understand this need some have to so assertively compare, critique and proselytize on who uses what font, and from where
Why would type designers who have their own fonts for sale via commercial webfont directories go out of their way to criticise (or even accuse of piracy) the designers of fonts on free webfont directories? I can’t see why they would do that.
Vernon, all you’re basically saying with the “crowd” vs. “court” metaphor is that Google Web Font being a pile of fonts with quality all over the place is intentional rather than accidental. If I already believe that “pile of fonts with quality all over the place” is a bad model for peddling fonts, that just makes Google deliberately tasteless as opposed to accidentally tasteless.
resort to gymnastics to re-imagine font files freely and widely available under opensource licenses as not really open source
As I’ve already said, an open-source license is not sufficient to make something open source. It’s not a matter of “gymnastics.” It’s a matter of meaning and substance.
don’t understand this need some have to so assertively compare
Google has made a particular claim about these fonts. I’m examining whether the claim is valid. (Or do you think Google should be exempt from this kind of scrutiny?) As I’ve already said, I don’t otherwise care what Google does, how many fonts they release, who uses the fonts, etc.
Why would type designers who have their own fonts for sale via commercial webfont directories go out of their way to criticise (or even accuse of piracy) the designers of fonts on free webfont directories? I can’t see why they would do that.
As I’ve already said, nothing here is meant as a criticism of the type designers who have contributed to Google Web Fonts. I care about the future of type design. What worries me is that up-and-coming type designers might see Google as their best or only option, fail to consider other options, and thereby stunt their growth as designers.
It’s incumbent on type designers who’ve been around the block to share what they know. If, having heard my pitch, those up-and-coming designers say “MB, you’re an idiot, I love Google Web Fonts,” I can live with that. At least they’ll be making an informed choice, not an ignorant one.
Mathew, everything i’ve said is my own opinion, it in no way should be read as the view of any other designer creating webfonts for the font directory. It especially shouldn’t be read as google’s view.
It’s heartening to see the parameters of your stance softening, but are you really still insisting that software freely and openly released under well established opensource licenses (GPL, OFL, etc), and used freely by millions of users under that license, isn’t ‘open source’? As a lawyer, are you saying that either the Open Font License or the Gnu Public licenses are not legally valid for licensing fonts? Have you contacted SIL or Gnu about your ideas? Curious about their position?
cheers –vernon
@anonymous
Why do you equate “crowd” with ‘lower quality’, ‘accidental’, and ‘pile’ ? Are you demophobic?
What I’m “really still insisting” is that the idea of open source necessarily incorporates certain ethics, practices, and values — or, as I call them, “essential qualities.” An open-source software license is just the final manifestation of those essential qualities. It does not retrospectively confer those qualities on a project that otherwise lacks them.
In this discussion, I’m not exploring the legal validity of any of these licenses. I’m simply observing that certain projects claim the mantle of open source — by using an open license — without otherwise living up to the values of open source. I consider Google Web Fonts, conducted under its current parameters, to be one such project. To me, that’s not good enough.
If that’s good enough for you, fine. But that position shrinks down the idea of open source to nothing more than file sharing. At which point open source just becomes a marketing catchphrase.
Mathew, thanks for clarifying your ideas.
I’d really like to pin this down properly with you, if possible, because, i think you are pointing at something very important. If you, as a lawyer, with some expertise in type design, is making serious statements claiming that a significant amount of fonts released under opensource licenses, such as the OFL, “aren’t really open source”, then i think we need to sit up and listen to you. I’m certainly listening closely, because i see that if opensource licenses are being used by designers to publish ‘not really opensource’ fonts more than to publish opensource fonts, then surely the licenses become somewhat undermined as valid opensource font licenses? That is what you are saying, isn’t it? That these licenses are being used to add false credence to a position that adversely “shrinks down the idea of open source to nothing more than file sharing”, and that despite the license under which they are published, the fonts are ultimately “not really opensource”. Is that really your claim, Mathew?
But are licenses such as the GPL and OFL really being widely (mis)used in this way by designers (on a pretty large scale, i would say, looking at your claims)? Are you really certain that designers like myself, are developing and publishing fonts under these licenses only to “claim the mantle of open source” and/or just to give us a “marketing catchphrase”? Are you sure about that? How am i doing that exactly? I’d like some evidence from you on that claim, as it is quite a claim.
And, i’m still curious if you would include fonts, published under the OFL, by SIL, in your claim of “aren’t really open source”. As far i know fonts published by SIL are no more, or, no less, encapsulating of your ‘essential qualities’ as fonts that i publish under the same licence.
Many thanks
–vernon
You’ve overstated the scope of my argument. I’m only talking about Google, because Google is explicitly claiming that “All of [our] fonts are Open Source.” Could my argument be extended to other organizations that are engaged in open font development? Perhaps. But I haven’t done so here.
Nor am I saying that open-source licenses per se are being undermined. Complying with a license is the easiest part of open source. The hard part is everything that comes before — what I’ve called the seven essential qualities. What’s being undermined is open source as a broader idea.
To be fair, if we went over to the software arena, we’d also find projects under open-source licenses that are not especially open source in spirit. But in software, we also have plenty of good examples of how open-source development is supposed to work. In the font arena, we don’t. So the weak interpretation of open source runs the risk of preventing a stronger interpretation from emerging.
As for the evidence, I’ve already explained it in detail. The biggest issue is Google’s emphasis on quantity over quality. No one has seriously disputed this. I’ve heard a few variations of “Look over here — these 15 fonts are really good!” OK, but what about the other 500? What is Google’s rationale for releasing hundreds of fonts that apparently no one feels comfortable defending? One can’t address the bad facts by ignoring them.
You invite me to criticize designers, which I’ve said I will not do. But I might ask you (or any designer of ostensibly open-source fonts) — do you think open source means something more than file sharing? If so, what? And how does your work live up to those values?
Mathew, thanks for more further clarification.
As i’ve stated before, my comments and views are wholly my own, as is my decision to release fonts under opensource licenses. I’m more than happy to respond personally to the concerns you have about them. Just shoot! I’ll possibly defend them too.
My view of your ‘essential qualities for opensource development’ concept, is that it clearly reflects someone with a very ‘top down’ approach. It probably explains why i relish an opensource model, and you, maybe less so. To me, your checklist is a pretty typical view of someone not used to working with opensource content & users in their day-to-day work. What are your experiences of your concept in your own opensource projects? how do your ‘esential qualities for opensource’ invect your own opensource output? There’s no substitute for real world, day after day, frontline experience, so I am genuinely interested how your concept works for you in the real world. Personally i’d be worried that your checklist would hinder as many opensource developers & users as it might help or attract.
Imho the full breath of opensource models have their place, as does the full breadth of proprietry models. I bet that developers are best to use the working model that they work ‘happiest with’. Then a project can concentrate on creating stuff and users either respond, or they do not. Rewards come, or they do not. You pack up, or you keep going. It’s Darwinian; if it fits, then it survives and reproduces. Personally, i adopt a bottom up, opensource model; high on action, low on semantics. I like the way that works at the moment, i like the way users respond, and i like the rewards. I wouldn’t use that model if it didn’t work for me. With this approach i am also free to change/adapt/reform/abandon if i feel anything starts to not work. I’d say that’s another asset of a bottom up approach; nothing get’s ‘too precious’, there are few over-arching conceptual burdens, and you can easilly scrap work and start over. Also, because it is such an open model, it allows collaboration and input from any direction, from anybody, there’s no ‘do you pass the Butterick 7 Essential Qualities test?’. To me your model, would close down that openness way too much. As you say, a project is either trully ‘open’ or it is not, the guage of that is simple; can any user, at any time, look at/get/use/adapt my product and it’s source code. My concern is that your model would impede too much on that openness for my liking.
cheers
–vernon
> And how does your work live up to those values?
I have opened all my projects now, in a way that’s easy for anyone to participate, send suggestions, edit the source files and post them back, etc:
http://www.impallari.com/projects
I hope this new interface will enable wider participation and collaboration.
Also, will be hosting guest projects for anyone interested.
I am really suprised by the amount of critisim of GWF. Ok, I wasn’t aware of how many things actually work @GWF (so thanks Matthew for this interesting insight) but still – even though the author makes some good points – my feelings about this project are rather positive.
I don’t want to argue about the quality of the fonts, too many great designers participate in this discussion. But reading these comments made me feel like Michelangelo and Van Gogh are visiting a small stationery store and complain about the poor quality of brushes and canvasses. I think the fonts @ GWF aren’t ment to be the next corporate font for Deutsche Bahn or Bank of America. But: There are some good entries, which let us take a break from starring Verdana, Georgia and the best font in the world aka Comic Sans.
I also wanted to mention what services like Google Web Fonts, Typekit & Co have changed for me: I am a webdesigner, working on rather small projects. Few years ago it was almost impossible (well, at least very hard) to implement custom fonts on a website. There were some options to overcome technological hurdles (using sIFR, Cufon etc.) but that wasn’t really conveinient, plus there were no clear licensing models for using fonts in the web. I asked directly at the foundries a few times, but i never got an offer affordable / rationally suitable for my clients.
Since 2009/2010 things began to change. Suddenly it was much easier to implement fonts by adding few lines of code (@GWF you just need copy one line of CSS!). The browser-support for fonts became better and better. Online typeface-libraries began to offer clearly priced web-licences and detailed instructions how to use them. It’s much easier to present the benefits of a nice webfont to a client and estimate the costs.
Now i use webfonts on almost every webproject, either GWF, Typekit or a EOT/WOFF license. Recent changes allowed me to extend my service portfolio, I can offer better products to my clients. I hope this new enthusiasm and interest in web typography will also have a positive influence on sales @ fontfoundries and designers.
In my eyes Google plays a part in this process of bringing type to the web. And it was really about time we start this journey. Google is doing it their own way (whatever that means), but hey, they are right to do so, because the *do* something. If you are *doing* something, you can decide how to do it.
This is a very interesting debate.
I really think that GWF has a lot of good fonts, and some great fonts. It would be nice if Google could be more of a mentor and guide to some of the unexperienced designers, but if they don’t want to do that, designers will find other ways to help each other and inspire each other.
What Pablo does on his page is great! Expanding “Raleway” is exactly why these fonts were made Open. I remember someone expanded the “Chunk Five” font which started with a very restricted set of characters. I don’t have the knowledge to edit fonts myself, but I do write comments or e-mails to designers who ask for feedback, like Vernon on his blog.
Hi Butterick,
I think you’re wrong about open source.
I’m an amateur coder. I don’t have no university or any certificate. However I have some open source projects ^^ If you need proofs, here is one of mine: http://code.google.com/p/android-filechooser/
I pushed my passion into the projects. So I don’t care if they are craps to someone. That’s open source. As like as you have a car, and your friend needs a car, he or she borrows it. Yes, if you like it, use it. If you see bugs, feel free to fix. If you don’t like it, that’s ok.
Open source doesn’t need quality. It needs passion. When you have passion, you do the best. That’s “quality”. Have you ever paid Linus Torvalds a cent? I think he’d never think about that. Do people see that in the first days of his works, no one thought about nowaday?
If Google want to buy me some beer, or buy me a helicopter, that’s fine. I’ll be very happy if it’ll be a helicopter
But if there is nothing, then no problem.
If there are libraries which have same functionalities as mine, and Google pay their founders. That’s ok too. Why? Because when I’ve had the ideas, I’ve thought about doing them, money-has-been-never-being-a-condition.
About Google Web Fonts. I don’t care how many people in the world can produce “best fonts”. To be honest, that sucks.
There-is-no-limitation.
A man coming from Africa can produce best fonts (no quotation marks). I don’t care if one of them was born in Silicon Valley, or was born in Vietnam, my country — one of the last communist countries in the world. I see by-my-own-eyes — the fonts are beautiful. So it’s ok. Download and use! To my standards, they’re the best. No need for American Standard.
If open source needed to be certificated before it is published to the community, then there would be no Fedora, Mandriva, Ubuntu, or Android…
And, I don’t work with fonts, but you’re welcome to be a committer with them. It’ll have fun
Sincerely,
Hai Bison
Nice article. I really enjoyed reading something with Charter/Charis (I cannot distinguish on screen)
Just one comment:
>Reality: Open source relies on benevolent dictators.
Not really absolutely true. Canonical is an example of what you mean, but Debian may be an example of a different point, which existed before Ubuntu and it seems to be that it will still be some years around
I just found this thread. My annoyance with Google Web Fonts have been echoed here numerous times: It’s a dumpster with hundreds of low-quality fonts. There’s no real way to make a request like “Show me only fonts with delta hinting” or “Show me only fonts designed for body test”—a strange deficiency for the king of search.
I’ve gone through GWF to try and find decent fonts with Delta Hinting. Ubuntu is pretty good, but it’s no Verdana, and its license is an unusual non-OFL one. Cousine is a beautiful fully delta hinted OFL font, but, alas, it’s a monospace. The PT series (PT Sans, etc.) is nice; it’s a shame that PT Sans Caption doesn’t have decent delta hinting (nor an italic/oblique).
I would much rather have one OFL-licensed font with delta hinting that is as readable on the screen as Verdana than 10,000 useless fonts. Unfortunately, I haven’t found one yet. And I’ve been looking for years.
If you’re looking for Delta-hinted fonts (or whatever other quality standard my be applicable for your intended application), perhaps you should consider paying a license for a professional font. There is only so much you can expect from fonts that have been designed by people in their spare time and then made available for free.
Do you give your work away?
Indeed. TANSTAAFL. I’m a software developer, and there’s a reason why my open-source program doesn’t have DNSSEC. Everyone wants a really great free web font, but no one wants to pay for it.
That said, I did look at the Kickstarter projects and there isn’t one for an OFL fully delta hinted screen font out there. But, realistically, a good delta hinted font will probably cost between $50,000 and $100,000 to pay the designers to develop—and I don’t think Kickstarter is able to raise that kind of money (Exo got $7,500).
Matt… you’re awesome. You can talk law, open source principles, typographic excellence, python, economics and the collective action problem all in one essay AND keep up with the comments. WTF? I started talking typography the other day to a fellow law student and their eyes glazed over in a matter of seconds.… I appreciate you and people like you in this world.
Erik Spiekermann. I’m getting somewhat star struck here. Sorry for that.
I think Sam could pay a license for a professional font with delta hinting. Myselft have spend quite a lot over the years. However, when it comes to Open Source projects, like GPL, i may need to ship it with a font with a license that is compatible with GPL.
”There is only so much you can expect from fonts that have been designed by people in their spare time and then made available for free.
Do you give your work away?”
This is true in most cases. However, there could be different. An example is the very software you are using on your blog.
WordPress. Lot’s of people are actually giving away their work and does not get paid for it (not everyone, but many). The result is progress. So, how do they get paid?
They get paid as everyone else working. But maybe not from Automattic or some other company involved with WordPress. Many of them are doing this at their spare time outside their ordinary jobs. The result is something millions of people are using.
However, a font project is not the same as a project like WordPress. And it’s hard to imagine 200 people working on a professional font at the same time.
I think companies like Google, if they actually are serious with Google Web Fonts should have a strategy with more commissioned work to bring in more great typographers to the project. While still be ”generous” about what fonts are included in the repo.
That way i believe Google Fonts will be more inclusive. If Aunty wants to use crazy font 1 for her webpage about hamsters. Fine.
If someone else wants to have fonts with ligatures, more styles than one, delta hinting and so on, they would have it.
Will it eat market shares from the various type foundries? I don’t really think so. Type foundries are mostly not marketing their business towards the web anyway. The few that do, will still have their own niche and audience.
Cheers. And keep up the good work (actually reading about you in the Swedish magazine Cap & Design right know).
Christopher, almost all the fonts in Google Fonts were commissioned for it, and the designers paid to make them.
[…] always on the make and always looking for opportunities has some pseudo open-source fonts at http://www.google.com/fonts/ – but ‘measured by professional […]
[…] always on the make and always looking for opportunities has some pseudo open-source fonts at http://www.google.com/fonts/ – but ‘measured by professional […]