November is Native American Heritage Month. This week, many Americans will gather for Thanksgiving, a holiday celebrating the “First Thanksgiving,” the fictionalized breaking of bread between the pilgrims (colonizers) and the Wampanoag people who’d inhabited the land around what is now Plymouth, Massachusetts, for over 12,000 years.
While it is vital to acknowledge and celebrate Indigenous cultures no matter the time of year, heading into this beloved yet problematic holiday with a challenge to broaden our awareness is fundamental.
What does this have to do with typography?
I ran across an incredible design and research program from the Netherlands-based foundry Typotheque, helping Indigenous communities reclaim and digitally preserve their language scripts. I spoke with Typotheque collaborator Kevin King. The Canadian designer, calligrapher, and educator is focused on support and research for minority languages through reform to the Unicode text standard, an effort he started while designing the typeface Mazina for his master’s design thesis.
Our conversation is below (lightly edited for clarity and length).
Covering Typotheque’s Zed typeface recently, I was astounded to learn that more than half of the 7,100 (at least) known world languages are endangered. I’d imagine that many of those at risk are centuries—perhaps, millennia—old Indigenous languages. Why is it important to preserve them, particularly in digital contexts such as Unicode?
Yes, indeed, Indigenous languages across the world – not only in North America – are at-risk of being lost within our lifetime, and the importance of Unicode towards the larger narrative of Indigenous language reclamation and revitalization is that without a stable basis for reliable text encoding on all computer devices and software platforms, it is not possible to ensure that remaining fluent speakers, and perhaps more importantly, young language learners, can have a consistent level of access to their language that leads to more engagement and ensures the success of learners to acquire the language and use it ubiquitously in daily life.
Unicode itself is not enough by itself; the Unicode Standard provides the standardized repertoire of characters that are available for encoding and character data to instruct the behaviour and relationships of the characters, but language tools and our software must implement the Unicode Standard correctly and comprehensively in order to make language access a true reality. This means that major operating systems and applications must also take care to support new character additions to the Unicode Standard and the character data. Keyboards must be available to input those Unicode characters, and fonts must be available that shape how the Unicode “text” should be represented typographically. This is in many cases trivial for “majority” languages across the world; however, for Indigenous languages, it is an all-to-common reality that there may be missing characters from the Unicode Standard, or, that software and language tools (keyboards and fonts) do not accurately support the way text must appear and behave in these languages.
How do you work with Indigenous groups; what does the collaboration look like?
The most essential component of working with Indigenous language communities is building a relationship together that is based on mutual respect and collaboration. We do this by first creating a protocol agreement that outlines our shared goals, values, and desired outcomes for the work, and the key that underpins all of the work is the collaborative nature of everything we do. When working together on a particular initiative, our role is to first listen to the needs of the community about the barriers they may face and to provide our technical knowledge in the form of possible actions to solve the problem. Then, only with permission, can we move ahead to execute a solution that the community has determined is acceptable for them.
Tell us more about your project with the Cherokee and Osage in Oklahoma.
Our projects with the Cherokee and Osage scripts are slightly different than our work directly with language communities such as the Haíɫzaqv community or the Nattilik community. In these projects, we are working with talented local type designers in each Nation to work together on developing new fonts for each script. Our Cherokee project is led by Chris Skillern, a skilled type designer from Tulsa, Oklahoma, and a member of the Cherokee Nation, who is designing new Cherokee fonts for Typotheque and also conducting research towards typographic preferences for Cherokee syllabary forms. Similarly, our Osage project is led by the talented typographer and designer Dr. Jessica Harjo of the Osage Nation. In this project, Jessica and I work together as a team to develop the Osage typefaces, and our goal is to understand ideal typographic lettershapes for Osage that allow for the best graphic representation of the script for reading.
What makes Indigenous scripts so unique, and what are the challenges in designing digital fonts for them? For example, many (though not all) Indigenous scripts are syllabic.
In the North American context, there are, of course, the wonderful and unique scripts that were developed specifically for Indigenous languages, first the Cherokee by Sequoyah, and then the Syllabics used by First Nations and Inuit communities in Canada, and then more recently, the Osage script. These are graphically distinct writing systems, and for many other Indigenous language communities, variations of the Latin script, with many integrated characters from the Greek script or phonetic notation systems, may be based on that script of European origin; however, they are inherently unique from European language orthographies using the same script.
Specimens from the November (top) and Lava (bottom) typeface Syllabaries
Indeed, these scripts and writing systems all come with their unique design challenges. One major challenge for all is the lack of support for any of these scripts in common font development software. This means that – unlike designing type for other well-supported scripts – it is not possible to open a font editor, populate a character set, and then start drawing glyphs. The designer has to first define a character set and possibly even resolve Unicode-level issues before beginning the design process.
Once one has a character set defined and has worked out the encoding side aspects, there is then also a knowledge issue, or perhaps better put, the lack of knowledge for how to design accurate typefaces that work as users expect and require their typography appear, and generally for how their orthography must work. For example, within the context of the Syllabics, a type designer needs to be aware of inherent orthographic and typographic conventions that are particular to this writing system that affect the logic of how a typeface in this script must work.
A case in this script is how much wider the word space character needs to be than the Latin script for the legible reading of Syllabics. However, both scripts use the same Unicode character for the word space (U+0020 SPACE) but have conflicting demands. Upon learning this, the type designer may recognize the problem and has several options for how to implement support for this, but they would be missing a key ingredient still in their knowledge of the situation: what practices do language users have when keying in that word space that would affect the design implementation? For example, to avoid a conflict between word space widths, we could create contextual substitutions via OpenType Layout features, which switches the desired glyph between both scripts. However, through our work speaking with many different Syllabics users across many different communities, we know that most users have developed a practice of entering a double spacebar when typing in Syllabics which solves the problem, and we do not have to allocate the time and energy to devise a solution for this but to be aware of the fact that Syllabics require this wider space.
We have tried to contribute to this knowledge by creating this GitHub repository, and we are currently working on a research project (Typotheque Indigenous North American Type) in partnership with First Nations communities that seeks to help build similar knowledge for many other languages and their orthographies that can then allow other type foundries to access this information and implement accurate support for these languages.
Left: A proof showing a comparison of the Lava Syllabics upright and cursive forms, in the Heavy master; Top right: An early sketch made by the author during the initial research phase of the project, exploring potential modulation structures that could be applied to the Lava Syllabics design; Bottom right: An example of the concept of rotation, which sits at the core functionality of Syllabics typography, for any language that uses the writing system.
As a foundry, Typotheque is committed to supporting digitally underresourced languages. How is this labor of love funded, and what are ways that the design industry (companies or individuals) can help and further the effort?
We are certainly passionate about this space of work, and it is an important part of what we do at Typotheque, not only for languages in North America but also for Indigenous and under-represented languages across the world.
All of the work that we do is completely funded internally by Typotheque by using revenue generated from retail font sales and custom project work for clients. In this sense, customers who purchase licenses for our fonts or hire us to do custom typeface work effectively help support this work and allow us to continue the effort. We have also created the Typotheque Club, which is a free club that features talks, rewards, and crowdfunding initiatives, and provides us with another avenue for generating funding for this space of work.
What is something surprising you’ve learned about Indigenous written languages generally (or a specific script) in this research?
Something that is perhaps surprising that I have learned is that – despite such rich orthographic and typographic diversity in the writing systems used by Indigenous languages in North America – the oral language is still always the most important aspect of the language.
I understand you’ve been interested in typeface support for Indigenous languages since your master’s studies. Where is your research taking you now; what’s a dream project you’d love to sink your teeth into?
I’m very grateful to work in this space of Indigenous language support and ultimately, language revitalization and reclamation, where the work has a direct, very tangible, and meaningful impact on people’s daily lives. It’s also part of contributing to society at large and using my design skills to positively support the important work that Indigenous language keepers and communities are undertaking. With that, the current project we are working on at Typotheque and have just begun – Typotheque Indigenous North American Type – would be something that embodies where I wish to focus my efforts, a project to work in partnership to overcome technical issues and understand typographic preferences and requirements with Indigenous communities, alongside looking towards projects designing and developing new and fresh typefaces that support Indigenous languages and their writing systems as standard and ubiquitous parts of these products.
More resources & reading:
November is a typeface designed for signage and information systems, but its orthogonal style is rhythmic in smaller contexts. Zed and award-winning Lava are two additional typefaces supporting Latin and Syllabic Indigenous scripts. Some of the process images included in our feature above are from King’s work on developing a secondary slanted style for Lava.
q̓apkiⱡ Magazine is a recently published, award-winning publication for the Ktunaza community in British Columbia, featuring both November and Lava.
King also wrote comprehensive guidelines for Syllabic typographic development.