Normal
0

false
false
false

EN-US
X-NONE
X-NONE

MicrosoftInternetExplorer4

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Table Normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:””;
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:”Calibri”,”sans-serif”;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:”Times New Roman”;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}

     B  I  T  N  A  P

  A  B  C  D  E  F  G  H  I  J  K  L  M

          N    

         O 

      P  Q  R  S  T  U  V  W  X  Y  Z

I hope my font, bitNap, shows up in the published version of this post.  It’s behaving weirdly.

One of the hardest thing to do when making a font is deciding what kind of font, especially after going through Lupton’s historical whirlwind of options.  So I opted for the constraint of the prompt she gives on page 58:

“Create a prototype for a bitmap font by designing letters on a grid of squares.  Substitute the curves and diagonals of traditional letterforms with rectilinear elements.  Avoid making detailed ‘staircases,’  which are just curves and diagonals in disguise.”

Not using curves and diagonals, especially for letters like s and z, presented the biggest challenge in making a bitmap font.  No, I should amend that statement:  The biggest challenge of making a font in a reasonable amount of time is perfectionism.  I had to be content with my shabby font.  People like Baskerville spend years designing inventive, transgressive fonts, which become old hat in a few years.  bitNap may not be impressive, but it’s mine.  I actually like my S quite a bit.