<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
  <channel>
    <title>Ben Crowder — #type-design posts</title>
    <link>https://bencrowder.net/blog/tag/type-design/</link>
    <atom:link href="https://bencrowder.net/blog/tag/type-design/" rel="self" />
    <description>Feed for blog posts tagged with #type-design.</description>
    <lastBuildDate>Fri, 13 Nov 2026 20:22:20 GMT</lastBuildDate>
    <language>en-US</language>
    <generator>https://bencrowder.net/</generator>

    <item>
      <title>Nicholas Rougeux’s digital edition of Daniel Berkeley Updike’s Printing Types (the first volume of w...</title>
      <link>https://bencrowder.net/blog/2025/9.23b/</link>
      <guid isPermaLink="true">https://bencrowder.net/blog/2025/9.23b/</guid>
      <pubDate>Tue, 23 Sep 2025 12:00:00 GMT</pubDate>
      <dc:creator><![CDATA[Ben Crowder]]></dc:creator>
      <description><![CDATA[<p>Nicholas Rougeux’s digital edition of Daniel Berkeley Updike’s <cite><a href="https://www.c82.net/work/?id=400">Printing Types</a></cite> (the first volume of which I read <a href="https://bencrowder.net/blog/2024/booknotes-3-23/">a year ago</a>). Perhaps my favorite of Rougeux’s thus far, and one I’ll be returning to over and over again. It’s so good. And that <a href="https://www.c82.net/printing-types/posters">type specimen poster</a>! The <a href="https://www.c82.net/blog/?id=100">making of post</a> is also worth reading.</p><hr class="feed-extra" style="margin-top: 48pt;" /><p class="feed-extra feed-mail"><a href="mailto:ben.crowder@gmail.com?subject=Re%3A%20Nicholas Rougeux’s digital edition of Daniel Berkeley Updike’s Printing Types (the first volume of w...">Reply by email</a></p>]]></description>
    </item>
    <item>
      <title>After a decently long stint with Literata as the font on this site, I’ve switched to EBC Garamond. I...</title>
      <link>https://bencrowder.net/blog/2024/9.1/</link>
      <guid isPermaLink="true">https://bencrowder.net/blog/2024/9.1/</guid>
      <pubDate>Sun, 01 Sep 2024 12:00:00 GMT</pubDate>
      <dc:creator><![CDATA[Ben Crowder]]></dc:creator>
      <description><![CDATA[<p>After a decently long stint with Literata as the font on this site, I’ve switched to EBC Garamond. It’s my personal fork of the 8 pt size of <a href="http://www.georgduffner.at/ebgaramond/design.html">EB Garamond</a> — I like thicker fonts that don’t feel quite so digital, and the 8 pt version has that. I’ve fixed some glyph collisions (in the small caps), modified some of the glyphs I wasn’t happy with (widening the /p/, for example), turned off some default ligatures, and fine-tuned the kerning. This is still very much a work in progress and there are still changes I want to make, but it feels ready enough for use here.</p>
<p>A note on process: I opened the original SFDs from the repo in FontForge and exported UFOs. I’m using Fontra (which I’m quite liking, by the way) to edit the glyphs, and I hand-edit the OpenType feature definitions in Vim. I use <code>fontmake</code> to generate OTFs and <code>pyftsubset</code> to convert them to WOFF2. And I have a little testbed HTML file that I use to check in-browser whether I’m happy with the changes. It’s a decent dev experience.</p>
<p>And goodness, this is fun. I’m having a blast.</p><hr class="feed-extra" style="margin-top: 48pt;" /><p class="feed-extra feed-mail"><a href="mailto:ben.crowder@gmail.com?subject=Re%3A%20After a decently long stint with Literata as the font on this site, I’ve switched to EBC Garamond. I...">Reply by email</a></p>]]></description>
    </item>
    <item>
      <title>Links #40</title>
      <link>https://bencrowder.net/blog/2021/links-40/</link>
      <guid isPermaLink="true">https://bencrowder.net/blog/2021/links-40/</guid>
      <pubDate>Fri, 19 Mar 2021 12:00:00 GMT</pubDate>
      <dc:creator><![CDATA[Ben Crowder]]></dc:creator>
      <description><![CDATA[<p><a href="https://daverupert.com/2021/02/the-web-is-something-different/">Dave Rupert on how the web is something different</a>. Celebrating the democratic nature of the web as a space for everyone, not just professionals. I like that.</p>
<p><a href="https://adrianroselli.com/2019/12/responsive-type-and-zoom.html">Adrian Roselli on responsive type and zooming</a>. Over the last few years I’ve become one of those people who scale text up. Not massively — not yet — and not always, but it very much makes a difference for these aging eyes.</p>
<p><a href="https://vietnamesetypography.com/">Donny Trương’s free online book on Vietnamese type design</a>. Mmm.</p>
<p><a href="https://noahpinion.substack.com/p/checking-in-on-the-global-south">Noah Smith on developing countries in the Global South</a>, which tied in nicely with my recent reading of <em>How Asia Works</em> (and mentions the book as well). Nice to see that Malaysia’s doing better than it was when the book was written.</p>
<p><a href="http://radio.garden/">Radio Garden</a> lets you browse worldwide radio stations via a map. Fun.</p><hr class="feed-extra" style="margin-top: 48pt;" /><p class="feed-extra feed-mail"><a href="mailto:ben.crowder@gmail.com?subject=Re%3A%20Links #40">Reply by email</a></p>]]></description>
    </item>
    <item>
      <title>I’ve decided to ditch Adobe’s Creative Cloud apps — Photoshop, InDesign, and Illustrator, mainly. I...</title>
      <link>https://bencrowder.net/blog/2021/1121/</link>
      <guid isPermaLink="true">https://bencrowder.net/blog/2021/1121/</guid>
      <pubDate>Sat, 23 Jan 2021 12:00:00 GMT</pubDate>
      <dc:creator><![CDATA[Ben Crowder]]></dc:creator>
      <description><![CDATA[<p>I’ve decided to ditch Adobe’s Creative Cloud apps — Photoshop, InDesign, and Illustrator, mainly. I never thought I’d say that, but they’re too expensive. Instead, I’ll be using Affinity Photo, Affinity Publisher, and Affinity Designer. It’s a fairly small one-time cost instead of a dreary, never-ending, money-sucking subscription.</p>
<p>(If/when I need to do motion graphics or video editing in place of After Effects and Premiere, by the way, I’m planning to use the free version of DaVinci Resolve.)</p>
<p>So far I’ve only actually used Affinity Photo, to texture the piece I released yesterday. Worked like a charm. The live split-screen preview when applying a filter is brilliant, and the file sizes are much smaller, too. (In Photoshop I’d regularly end up with a 1–2 GB PSB file. With Affinity Photo, it’s closer to 300 MB.)</p>
<p>As far as typesetting goes, I still expect to use TeX (Tectonic) on projects where it makes sense — it’s what I used on the wide margin study editions since typesetting each language individually would have taken much more time — but it’s nice to have Affinity Publisher for other projects. I’m planning to use it for the book of narrative poems I’m (slowly) working on. (I’ll be setting it with Hinte, a new typeface I’m designing in FontForge. More on that soon.)</p>
<p>With Figma doing most of what I used to use Illustrator for, I don’t expect to use Affinity Designer all that much initially. But the raster brush textures are intriguing. We’ll see.</p><hr class="feed-extra" style="margin-top: 48pt;" /><p class="feed-extra feed-mail"><a href="mailto:ben.crowder@gmail.com?subject=Re%3A%20I’ve decided to ditch Adobe’s Creative Cloud apps — Photoshop, InDesign, and Illustrator, mainly. I...">Reply by email</a></p>]]></description>
    </item>
    <item>
      <title>Links #34</title>
      <link>https://bencrowder.net/blog/2021/links-34/</link>
      <guid isPermaLink="true">https://bencrowder.net/blog/2021/links-34/</guid>
      <pubDate>Thu, 07 Jan 2021 12:00:00 GMT</pubDate>
      <dc:creator><![CDATA[Ben Crowder]]></dc:creator>
      <description><![CDATA[<ul>
<li><a href="https://www.raptitude.com/2020/12/own-the-tools/">David Cain on using paper dictionaries</a> — this resonates with me a lot, even though by profession I build web tools; I think this may be part of why, in my personal projects, I tend to prefer making discrete, downloadable objects like PDFs and EPUBs</li>
<li><a href="https://www.benkuhn.net/weekly/">Ben Kuhn’s weekly review habit</a> — great idea, planning to do something like this myself</li>
<li><a href="http://www.cmyr.net/blog/hyperbezier.html">Colin Rofls on a new hyperbezier pen tool</a> — excited to see where this goes, mainly for type design</li>
<li><a href="https://hotwire.dev/">Basecamp’s Hotwire approach to frontend dev</a> — I still need to look at this in detail, but it looks promising</li>
<li><a href="https://adactio.com/links/17712">Jeremy Keith on Hotwire and Turbo</a> — where I heard about Hotwire</li>
</ul><hr class="feed-extra" style="margin-top: 48pt;" /><p class="feed-extra feed-mail"><a href="mailto:ben.crowder@gmail.com?subject=Re%3A%20Links #34">Reply by email</a></p>]]></description>
    </item>
    <item>
      <title>Last year I posted a note about Curves, a Python type design library I was working on. At the time I...</title>
      <link>https://bencrowder.net/blog/2019/725/</link>
      <guid isPermaLink="true">https://bencrowder.net/blog/2019/725/</guid>
      <pubDate>Thu, 03 Oct 2019 12:00:00 GMT</pubDate>
      <dc:creator><![CDATA[Ben Crowder]]></dc:creator>
      <description><![CDATA[<p>Last year I <a href="https://bencrowder.net/blog/2018/633/">posted a note about Curves</a>, a Python type design library I was working on. At the time I’d given up on it, but I recently had some new ideas on how to make it more ergonomic. It now stands resurrected:</p>
<p><figure>
        <img src="https://cdn.bencrowder.net/blog/2019/10/curves-wip.png" alt="curves-wip.png" title="curves-wip.png" />
        
      </figure></p>
<p>Since I don’t think I mentioned it in my earlier post: the idea is that programming language constructs (functions, variables, source control, etc.) may make it easier to design a typeface, given the parametric and repetitive nature of that work.</p>
<p>It’s still a work in progress and very much an experiment — placing points in code rather than in a GUI will always have some friction to it — but it seems promising enough now that it’s worth finishing it and trying to use it for some actual type design.</p><hr class="feed-extra" style="margin-top: 48pt;" /><p class="feed-extra feed-mail"><a href="mailto:ben.crowder@gmail.com?subject=Re%3A%20Last year I posted a note about Curves, a Python type design library I was working on. At the time I...">Reply by email</a></p>]]></description>
    </item>
    <item>
      <title>Update on projects: I’m working on a short story. All of my story drafts of late have turned darker...</title>
      <link>https://bencrowder.net/blog/2018/633/</link>
      <guid isPermaLink="true">https://bencrowder.net/blog/2018/633/</guid>
      <pubDate>Wed, 31 Oct 2018 12:00:00 GMT</pubDate>
      <dc:creator><![CDATA[Ben Crowder]]></dc:creator>
      <description><![CDATA[<p>Update on projects: I’m working on a short story. All of my story drafts of late have turned darker than I’d like, so this one is intentionally not dark. Seems to be going better than the others.</p>
<p>I’m also partway through revising my next picture book. This one is a story (as opposed to <em>The Circle Book</em>, which was just a list of random things) and I’m excited. The urge to design a typeface for it has proven too strong to resist, though, so I’m working on that as well. The typeface is called Golly. I’ll post some screenshots soon (I’m almost done with the lowercase letters).</p>
<p>Sidenote on type design: I built Curves (a Python library for designing type, via exporting to UFO and compiling that to OTF) to see whether designing type in code works. Turns out it doesn’t. Even with easy previews (SVG and @font-face), the cognitive gap between the code and the points seems to be a little too much. I have some other ideas for type design tools that seem more promising, though. More on that later.</p>
<p>And I’m slowly working on the remaining reader’s editions (print/PDF of D&amp;C, Pearl of Great Price, and <em>Words of the Prophets</em>).</p><hr class="feed-extra" style="margin-top: 48pt;" /><p class="feed-extra feed-mail"><a href="mailto:ben.crowder@gmail.com?subject=Re%3A%20Update on projects: I’m working on a short story. All of my story drafts of late have turned darker...">Reply by email</a></p>]]></description>
    </item>
    <item>
      <title>Cantilever update 16 Sep</title>
      <link>https://bencrowder.net/blog/2013/cantilever-update-16-sep/</link>
      <guid isPermaLink="true">https://bencrowder.net/blog/2013/cantilever-update-16-sep/</guid>
      <pubDate>Mon, 16 Sep 2013 12:00:00 GMT</pubDate>
      <dc:creator><![CDATA[Ben Crowder]]></dc:creator>
      <description><![CDATA[<p>I’ve finished the initial drafts for all the lowercase characters in Cantilever and I’ve started working on the uppercase:</p>
<figure class="border"><img src="https://cdn.bencrowder.net/images/2013/09/Cantilever-Draft2.png" alt="" /></figure>
<p>Many characters are still missing — /B/, /H/, etc., as you can see — but it’s nice finally being able to use actual text (this is from George MacDonald’s <em>The Princess and the Goblin</em>).</p>
<p>What’s next: fixing the glyphs I’m still not happy with and fleshing out the rest of the uppercase. And then spacing and kerning! Then I can stop being bothered by the lack thereof.</p>
<p>Notes, in no particular order:</p>
<ul>
<li>I’ve decided that I’m designing for retina devices. Sure, it’s going to be several years before all desktops/laptops have retina screens, but man, it’s painful designing for lower PPIs. (So I’m doing most of my previewing on my iPhone.)</li>
<li>My current process for each glyph is to draw an initial lame draft in FontForge, export and preview, contemplate giving up type design forevermore, and then tweak the glyph and preview and tweak and preview until I’m happy with it. It’s working out okay, even for evil glyphs like /s/ (my first draft was absolutely pathetic) and /g/ (which is still somewhat pathetic but not as bad as it used to be). And /a/ was also a beast for several drafts.</li>
<li>I’m struggling with the uppercase. I’m going to look at some other fonts to see where I’m going wrong.</li>
<li>I finally got FontForge to compile on <a href="http://sourceforge.net/mailarchive/message.php?msg_id=31407980">OS X with Python</a>, so I’m writing some scripts to automate things (such as an export script that removes overlap and copies output files where I want them).</li>
<li>FontForge isn’t quite as bad as I originally thought it was. And the recent versions have user-customizable hotkeys.</li>
</ul><hr class="feed-extra" style="margin-top: 48pt;" /><p class="feed-extra feed-mail"><a href="mailto:ben.crowder@gmail.com?subject=Re%3A%20Cantilever update 16 Sep">Reply by email</a></p>]]></description>
    </item>
    <item>
      <title>Cantilever WIP</title>
      <link>https://bencrowder.net/blog/2013/cantilever-wip/</link>
      <guid isPermaLink="true">https://bencrowder.net/blog/2013/cantilever-wip/</guid>
      <pubDate>Wed, 04 Sep 2013 12:00:00 GMT</pubDate>
      <dc:creator><![CDATA[Ben Crowder]]></dc:creator>
      <description><![CDATA[<p>A couple weeks ago I started on a new typeface I’m calling Cantilever. Originally I thought I would sketch out the characters on paper and trace them, like I did with <a href="https://bencrowder.net/type-design/tag/pigna/">Pigna</a>, but I’ve ended up just drawing everything so far directly in FontForge. The initial few characters:</p>
<figure class="border"><img src="https://cdn.bencrowder.net/images/2013/09/Cantilever-Draft1.png" alt="" /></figure>
<p>Funny how characters can look semi-okay at large sizes but then not at all at text sizes. I went through several iterations to get something I actually liked:</p>
<figure><a href="https://cdn.bencrowder.net/images/2013/09/CantileverCharacterProgress.png"><img src="https://cdn.bencrowder.net/images/2013/09/CantileverCharacterProgress-800.png" alt="" /></a></figure>
<p>Since I’m intending this for use as a web font, I ended up writing a small JavaScript/HTML app to let me preview my work in-browser, both on desktop and on mobile. It lets me switch between different versions (so I can see if I’m making progress) and also different text blocks. (And of course I can tweak the size and line-height.)</p>
<figure class="border"><a href="https://cdn.bencrowder.net/images/2013/09/CantileverPreview.png"><img src="https://cdn.bencrowder.net/images/2013/09/CantileverPreview-800.png" alt="" /></a></figure>
<p>And here’s where Cantilever is right now (version 008):</p>
<figure class="border"><img src="https://cdn.bencrowder.net/images/2013/09/Cantilever-008.png" alt="" /></figure>
<p>There’s still a lot to do (fleshing out the rest of the characters, spacing and kerning, etc.), but overall I’m happy with the direction it’s going.</p><hr class="feed-extra" style="margin-top: 48pt;" /><p class="feed-extra feed-mail"><a href="mailto:ben.crowder@gmail.com?subject=Re%3A%20Cantilever WIP">Reply by email</a></p>]]></description>
    </item>
    <item>
      <title>Thoughts on font editor design</title>
      <link>https://bencrowder.net/blog/2013/thoughts-on-font-editor-design/</link>
      <guid isPermaLink="true">https://bencrowder.net/blog/2013/thoughts-on-font-editor-design/</guid>
      <pubDate>Fri, 23 Aug 2013 12:00:00 GMT</pubDate>
      <dc:creator><![CDATA[Ben Crowder]]></dc:creator>
      <description><![CDATA[<p>As I start getting more into designing type, I’m finding that I’m not as happy with FontForge. It works, yes, and I can design fonts with it, but it’s not beautiful, aesthetically or functionally. It doesn’t <em>sing</em>. It also has a lot of friction that slows me down. I’ve looked at the other font editors out there — FontLab, RoboFont, Glyphs — and they don’t really do it for me either. (Nor are they in my budget at the moment.)</p>
<p>I realized I’ve been spoiled by Vim and Blender, both of which have steep(ish) learning curves but which also are incredibly rewarding and efficient for power users. I want that kind of a tool to use when designing type. So, because this is me, I’m going to build one.</p>
<p>Well, sort of. I’m going to talk through the design out loud on here as I go along, occasionally building prototypes to better explain what I’m getting at. I’m sure at some point I’ll actually build it, since I already want to use it instead of FontForge, but for now I need more experience building type with existing tools so I can better know where the friction points are.</p>
<p>I’m calling it Curves, and yes, it’s partly tongue-in-cheek. Here’s a brief overview of some of the ideas behind it (some of which are already in existing font editors):</p>
<ul>
<li><strong>Power tool for advanced users.</strong> Reading about Douglas Englebart’s philosophy on computing has gotten me itching to make power tools instead of newbie tools. There’s nothing wrong with newbies, but I’m more intrigued by the idea of focusing on power users. Learning curves are okay. (Weak pun semi-intended.)</li>
<li><strong>Web-based.</strong> Originally I wanted to make this a desktop app like Vim or Blender, but the more I looked into it, the less interested I got (C/C++ no longer appeal to me, and doing the UI in OpenGL to be cross-platform would put me at a lower level than I’d like, since I didn’t really like any of the OpenGL UI toolkits I looked at). Besides, all my recent experience is in web stuff, and being able to edit fonts from anywhere will be nice. (I think seeing <a href="http://tridiv.com/">Tridiv</a> yesterday helped cement this decision for me, by the way.) Also, since web fonts are one of the main targets of an app like this, being able to load and preview the fonts in-browser will be a big plus. And web services have a lot of potential.</li>
<li><strong>Panes.</strong> I really, really love Blender’s windowing system, with non-overlapping panes. (Vim has something similar, though I don’t really use it that much.) I also love being able to easily store different layouts for different uses. With type design, this kind of setup feels like the right choice and would make it so much easier to switch between different parts of making type (designing glyphs, spacing/kerning, previewing text, OpenType features, etc.).</li>
<li><strong>Heavily keyboard driven.</strong> I’m thinking about possibly using chording and/or sequences (the latter ala Gmail, thanks to <a href="http://craig.is/killing/mice">Mousetrap</a>). Everything customizable, of course. At this point I’m thinking of borrowing Blender’s shortcuts for selecting (‘a’), moving (‘g’), scaling (’s’), and rotating (‘r’) points, since they’re all on the left hand, which frees your right hand for the mouse. But we’ll see.</li>
<li><strong>Command line.</strong> I don’t mean running it from the Unix command line, but rather that I want a command line as an integral part of the app. Command lines are really, really powerful, and the idea of one specifically tuned for designing type makes me giddy.</li>
<li><strong>Search.</strong> Not just searching for glyphs by name, but a powerful query syntax so I can easily get a list of glyphs wider than X or with left sidebearings smaller than Y or what have you. And saved searches, of course, like smart playlists in iTunes.</li>
<li><strong>Scripting.</strong> Of course. Python or JavaScript. I’m looking forward to being able to generate kerning pairs via Python rather than having to do that outside of the app and paste the resulting pairs in. Or being able to script a set of things to do just before exporting to OTF (like removing overlap and checking for points at extrema and stuff).</li>
<li><strong>Focus on designing text faces for use as body copy.</strong> I’m still not sure what that actually means in practice, but some ideas are: previewing pages of text instead of just lines; editing and previewing the italic and bold weights together with the regular (rather than as separate fonts); programmatic relationships between regular and italic and such; visually edited components that can hook together intelligently and automatically remove overlap on export.</li>
<li><strong>UFO.</strong> No, not flying saucers. The <a href="http://unifiedfontobject.org/">Unified Font Object</a> format is a nice XML-based schema that already has support in most existing editors and feels like a good platform to build on. (Besides, <a href="http://robofab.com/">RoboFab</a> can already read and write it.)</li>
<li><strong>Great OpenType feature support.</strong> One of my beefs with FontForge is that I have to use its UI for OpenType features. I’d much rather use Adobe’s text-based feature file format. Yes, FontForge can import/export it, but it’s not FF’s native way to edit OpenType, and I wish it were. (I, uh, like text.)</li>
<li><strong>DSL for editing glyph points.</strong> Visually drawing glyphs is nice, but I want to have a text editor pane beneath my glyph with code for that glyph that I can edit. (Text can be nicer for precision editing.) This would probably be a small domain-specific language. I’ve also thought about integrating it more completely — a fully-fleshed out parametric type design language, kind of like Metapost. The trick would be finding the sweet spot between writing parametric code and designing visually. I have some ideas for this that I’m excited to explore.</li>
</ul>
<p>There’s more (I’m very interested in finding ways to improve the UI for drawing Bézier curves), but that’s quite enough for now.</p><hr class="feed-extra" style="margin-top: 48pt;" /><p class="feed-extra feed-mail"><a href="mailto:ben.crowder@gmail.com?subject=Re%3A%20Thoughts on font editor design">Reply by email</a></p>]]></description>
    </item>
    
  </channel>
</rss>
