-
Typographical Problems for Console Frames 3.1
I wanted to make some notes about choices I’m making on Console Frame Typography. The two main goals of 3.1 are:
- Make everything more accessible. Ex: Make most frame printable on 8.5×11 paper. Make all fonts readable on the same.
- Formalize symbology of all elements. What do they stand for? How much meaning can they convey? How do we standardize for reliable remembrance and interpretation?
My first version of [5] Calling Into Gifts was not readable when printed — especially the scriptures from Jeremiah 1. I noticed when doing [1] Mercy Mission and there I made the description fonts much bigger. Here are some of my conclusions:
- Anything smaller than 10pt in Mukta is hard to read. 6pt Audiowide is OK for some non-essential elements like verse numbers.
- Mukta is a very nice, simple, sans font — but it has no italic which limits the diversity of text on a frame with a lot of that font. I’m thinking of switching to Deja Vu Sans which has “Oblique” and “Oblique Semi-condensed”. It’s not a Google Font though, so it can’t be served through the GFonts server. (Only important for web apps.) Maybe the best would be use Noto Sans which is similar. Noto is part of a Google project to create a universal typeface.
fonts.google.com
Mukta is a Unicode compliant, versatile, contemporary, humanist, mono-linear typeface family available in seven weights, supporting Devanagari, Gujarati, Gurumu
-
0 Replies
Sorry, there were no replies found.
Log in to reply.