<?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>#cantilever posts — Ben Crowder</title>
    <link>https://bencrowder.net/blog/tag/cantilever/</link>
    <atom:link href="https://bencrowder.net/blog/tag/cantilever/feed/" rel="self" />
    <description>Feed for blog posts tagged with #cantilever.</description>
    <lastBuildDate>Fri, 17 Apr 2026 23:19:59 GMT</lastBuildDate>
    <language>en-US</language>
    <generator>https://bencrowder.net/</generator>

    <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 via 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 via email</a></p>]]></description>
    </item>
    
  </channel>
</rss>
