{% extends "base.html" %} {% block meta_title %}Glyphviewer Documentation{% endblock %} {% block title %}Glyphviewer Documentation{% endblock %} {% block main %}
Glyphviewer is a web application that analyses web font files.
For those unsure about the meaning of "glyph", "font", and "web font", a small glossary is provided at the end.
Glyphviewer analyses font files, not fonts per se. (A font may consist of multiple files.) Permissible formats are TrueType (.ttf), OpenType (.otf), and best of all, Web Open Font Format (.woff). WOFF is preferred, because font data is compressed by design, resulting in quicker download.
Other controls present are:
To finish, users hit the Submit button.
If Glyphviewer succeeds, it will generate a page with the following sections.
Glyphviewer will display an error message when it fails. There are several reasons for failure.
These are several limitations built in to Glyphviewer.
Glyphviewer depends on the following software:
Once these libraries have been installed, the next stage is to install Glyphviewer via the following command:
pip install glyphviewer
The next stage is to add "glyphviewer" to your INSTALLED_APPS list in settings.py, and add the desired URL in one of the urls.py files.
The final stage is to populate the directory with fonts where you display your chosen font or fonts. The Glyphviewer application comes with its own set of fonts adapted from the Free UCS Outline Fonts; they have been converted to WOFF form for quicker download. These can be moved into the correct directory via the following shell command:
python manage.py collectstatic
The font files wil then be moved into the {STATIC_ROOT}/glyphviewer/fonts/ directory, and the browser will read the files from the {STATIC_URL}/glyphviewer/fonts/ folder.
Note: it is not mandatory to run the collectstatic command. However, if there are no font files in the above directory, then Glyphviewer will only be able to read remote files.
The HTML template files in this application have been redesigned to work with the Mezzanine CMS. The redesign removed any explicit references to particular stylesheets found with earlier versions. The app (and the fonts) are released under a GNU general public license. If you wish to do any changes, pop over to the GitHub repository for the app.
I created Glyphviewer as a tool to examine the character repetoire of web fonts. It is easy to find fonts online; it is harder to find out exactly what characters they support. Almost all contain standard capital letters like "A", "B" and "C", and that's not hard to discover, because those are among the first characters to be advertised by the foundries. It's harder to find out how much support a font has for more unusual characters like (say) "ŋ". One could install a fonts on the computer, and inspect it in a tool like "Character Map", but this is laborous and time-wasting.
So I created a tool that could analyse a font if it was located somewhere on the World Wide Web. Font makers often display their fonts using web pages, and even provide a place where people can type text and see it displayed using the typeface. All one has to do to analyse it is examine the attached cascading stylesheet for a link to the font file, and place its URL in Glyphviewer.
This application was designed in response to and in reaction to Google Web Fonts, which came out in 2011. The idea is wonderful: tens of web fonts available for access and download. A laudatory effort - except that it doesn't accurately show the full repertoire of characters for each font. Take Lato - a lovely font, and comes in 10 variants too. Now look at the character set Google Web Fonts displays for it. Does it show the "Ł" and "ł" it supports? This omission is inexcusable two years later, given that the creator goes by the name of Łukasz Dziedzic. Google – lift your game.
The primary inspiration for this is Mark Pilgrim, who wrote a blog post called "Fuck the foundries" in 2009 (before yanking it off the net two years later). His essay and/or rant got me interested in web fonts in the first place, as did his use of the utterly superb web font Essays 1743 in Dive into HTML5. Thanks to John Stracke for coming up with the "Essays" typeface in the first place.
I also have to acknowledge the developers of the libraries used in the making of Glyphviewer. A special shout out goes to the folk at TypeSupply who decided to open-source their code. It wouldn't have been possible without them. I must also acknowledge the Free UCS Outline Fonts project for providing the fonts used in this application.
Copyright © Peter Murphy 2011, 2012, 2013, 2014.
{% endblock %}