Helvetica Semi-Mono (?)

Hi! Here to make my random reappearance.
I’m currently coding a web portfolio (as a musician) using MD IO as the heading font. I’ve admired Covik Sans Mono and its use of a three-width system, and wanted to use it as the body font, but I felt it had too strong of a character as a pairing. Since this is a pretty niche category, I thought it would be interesting to take a crack at it using specimens of metal type Helvetica as a base, since I’m pretty bad at designing fonts otherwise. (Side note: I did discover Fragment Mono, but the texture looked unpleasant with the increased x-height in my opinion.)
I just started this yesterday, so any feedback would be much appreciated!

Comments

  • Two things jump out at me: the space character feels very narrow, and your diagonals are unbalanced in thickness – v, w, x, y and z are doing different things with weight, as does K. There’s more – bunching in diagonal apexes, spine of S being quite dark – but that’s where I’d focus right now.
  • I think I would first determine the relationship between x-height, cap height, the monospace width and the widths of the different letters themselves. It helps to limit the design on a bunch of charcteristic key letters so you don't have to design the whole alphabet while figuring it out. Right now some of the uppercase seem too condensed (which is maybe why Fragment Mono lowered the cap height, at least I saw this in other monospace fonts). Same for the lowercase. It seems a bit random right now and some more balance would benefit the design. It might be worth rethinking your system since i and j occupy a narrow space but then r,f and t occupy the normal monospace width despite being narrower letters in the original Helvetica. 
  • Also Semi-Mono as a term might be a bit confusing. IIRC Dynamo used it first as a term for an intermediate style between a monospace and a proportional style which is not really what you're working on.
  • John Hudson
    John Hudson Posts: 3,547
    Another way to approach unitised widths is to imagine rasterisation of the outlines at a particular bitmap size, and then set the advance widths to hit full pixel boundaries (this is easiest if you set the UPM size to be equally divisible by the notional bitmap size).
  • Evie S.
    Evie S. Posts: 83
    I feel like I should have clarified more in my original post. I’m using a three-width system in integer units (1 unit, 2 units, 3 units). I felt Covik Sans Mono did a good job with its implementation, and I took heavy inspiration from its system. I also felt like Neue Haas Grotesk Mono did a good job while keeping the x-height the same as its proportional counterpart. However, when I tried Fragment Mono, something was lost. It reminded me of something Kris Sowersby said in his writing about The Future: changing the proportions changes the essence of the typeface. I think 
    So from that, my observations: first, Covik Sans Mono works well with a half-unit space. Perhaps what I’m missing is a looser spacing overall to accommodate that narrow space character. Secondly, Neue Haas Grotesk Mono has narrower characters than the ones I have designed, even in the capitals. That was my compass for how narrow I could push things, but maybe I have to push wider for more comfortable reading.
    I agree that the drawing, weight, and overall proportions are very inconsistent right now. Early, I tried pushing /f/r/t into the one-unit space and it did not look good:
    I don’t have any updates on the typeface, but from all of your comments it seems I should explore overall width/spacing and explore adding more width classes.
  • Covik Sans Mono uses 300, 600, 900 units as widths, i.e. strict multiples of its minimum width. This results in a particular spacing where different letters start in the same horizontal position in consecutive lines:
     
    But even if you want to keep 3 overall widths, you could pick different ones, e.g. 400, 600, 800. The pattern of where in a block of text the letters align will change, but maybe it will be a better match for your typeface.
  • Nick Shinn
    Nick Shinn Posts: 2,313
    While still maintaining the rigour of the 3-width system, it would be possible to nuance spacing by contextual alternates, in which glyphs would be placed left, right or centre in their space, depending on the adjacent characters. 

    For instance, 

    sub f' f by f_left ;
    sub f_left f' by f_right ;

    This suggestion would apply to your one-unit /f/r/t system.
  • Evie S.
    Evie S. Posts: 83
    edited November 6
    Here’s a quick exploration of a six-width system. For ease of implementation, I used Nimbus Sans as a base, which I would redraw if I want to take this more seriously. The base unit is 150, with glyphs using 300/450/600/750/900.

  • Nick Shinn
    Nick Shinn Posts: 2,313
    Yes, that’s what I mentioned above. It’s especially useful for double-m; it works because you never get three /m’s in a row, and the adjacent letters are usually vowels. 
  • Nick Shinn
    Nick Shinn Posts: 2,313
    Actually, there is a triple-m word—the interjection “mmm.” 
    I was recently considering that for a typeface name, but as usual someone else had beaten me to the punch!
  • Evie S.
    Evie S. Posts: 83
    Thanks Nick Shinn and Stephen Coles for the advice! I’ll definitely try shift kerning, but I want to make sure the spacing works as is too. I’ve just redrawn the six-width from scratch. I tried to also improve the drawing quality and internal consistency.

  • John Hudson
    John Hudson Posts: 3,547
    You seem to be doing a pretty good job, but it’s still basically just Helvetica. I am wondering what is the point of this? You are demonstrating some technical skill, but why start with someone else’s design?
  • Evie S.
    Evie S. Posts: 83
    edited November 11
    As with all my type design endeavors, there is really no point to this. I’m a musician first, graphic design is somewhere down the list, and type design is nothing more than a hobby. A friend commented that my portfolio’s pairing of MD IO and Die Grotesk looked off—I maintain it’s a fine pairing, but it gave me an excuse to explore this avenue of Helvetica with a unit system.
    And ultimately, this isn’t really an experiment of creating a new typeface, this is an exploration of unit systems. I’m ultimately neutral on Helvetica in general. Overused, yes, often inapt, yes, but it’s still one of the most compelling neo-grotesques in my mind, and certainly one of the most neutral ones.
    If you want a pretentious answer, I think digital Helvetica always looks a bit stilted with its vestigial width system from phototypesetting. I made this as an experiment that draws more closely off the metal type with tighter spacing while also embracing the unit width system as an exaggerated feature.
  • Nick Shinn
    Nick Shinn Posts: 2,313
    edited November 10
    I’ve used “shift kerning,” to nuance monospace fonts, very sparingly—because it does tend to contradict the fundamental principle of the genre!

    However, Covik Sans Mono posits a clever leveraging of constraints-based design space.

    The sample you showed, Evie, of mixing “off the shelf” Helvetica glyphs, both Normal and Condensed, seems to me the most promising aspect of this investigation. Perhaps you could bump together the concepts of a limited number of unitary widths, with a limited number of variable font horizontal scale instances, and see what happens?
  • Craig Eliason
    Craig Eliason Posts: 1,486
    To me the /w, the /M, and especially the /W get black spots at the joins, so that their strokes wind up looking tapered in the middle
  • Nick Shinn
    Nick Shinn Posts: 2,313
    edited November 10
    In that case, it would seem that bold weight is most promising, as it minimizes the obviousness of different stroke widths—Adrian Frutiger, for instance, was not afraid to put narrow strokes in M and W, in the heavier weights of his sans serif designs.
  • Evie S.
    Evie S. Posts: 83
    Nick—I have considered making a variable font with width, if only to test various options. I just wonder what the best way to proof changes is. What I really wish I could do is proof with a variable font with changes to a character propagating everywhere. (i.e. every /a in the project gets width 600, every /f 300...) It seems like something that could be scripted, but I’m still on Glyphs 2 and have no intentions of updating.