The original version of this font seemed to have a problem with line spacing while I used Word® . A space was automatically inserted before ; and : and occasionally the , . For a reason I don't undertand any line of text using these glyphs slipped down a few pixels which made the pages of text look untidy and reading quite unpleasant.
I haven't seen any reason for this, found no slipped bricks below the base line or above the highest diacritic's edge nor did I see a brick at the left or right of a glyph nor did I 'misalign' glyphs. In desperation I have changed the position and shape of the 'problematic' glyphs as well as some descenders, ascenders and height of some diacritics. I'll check tomorrow if this has improved spacing. BTW, this problem doesn't show up in the font preview of the Fontstructor nor in the 'My Fontstructions - user input'
It is possible that my eyesight is bad, or that I was too tired when checking this font and its parent version. If you happen to spot or know what caused this erratc line spacing please let me know, thanks🤝
This is a cloneA different attempt at recreating the lettering of the RISO logo and inspired by the custom type featured in a Gaji periodical by Corners Studio.
I've drawn a similar typeface previously in Illustrator but with a varied set of glyph styles called Risalto, free for download in my font bundle.
Gob Pixi is an amalgamation of different experiments with colour, display type and visual effects throughout the years of working with a comfortable, personal design palette.
Having been obsessed with grain textures and primary + secondary colours throughout the start of 2020s, I was moved to translate that into typography after seeing Kilotype's Lofi Forest "fizzy-fying" an otherwise sharp-looking Roman/Serif.
Also, I have worked on a type project that got me to layer different coloured shadows and highlights above each other, so this is my attempt at translating that effect onto another typeface that I've shelved for quite a while now. (I happened to come up with something similar to Get Yourself Connected by chance and didn't know what to make do with it.)
Newt is a spinoff from Salamander but reduced to a 2x2 grid system. Originally planned for 2023's iteration of 36 Days of Type, but later scrapped due to time constraints.
Available to download for free as part of a font bundle over here.
See more:
https://fontstruct.com/fontstructions/show/989729/fraktur_refined
Chrysalide Old Face | FontStruct
https://fontstruct.com/fontstructions/show/2629304/echo-pixel-garalde-cyrillic
Garamond Italic SP | FontStruct
fs Fermat | FontStruct
RuneScape Large | FontStruct
This is a clone of Book OldSee more:
https://fontstruct.com/fontstructions/show/2344057/touchdown-wip
https://fontstruct.com/fontstructions/show/29720/konstruct_1
https://fontstruct.com/fontstructions/show/1653608/nardo-1
This had the numberscomp tag on it at some stage, so still shows the numerals first in the gallery pages. I wasn't happy to share it until now however. I used a combination of connected and custom made bricks. Alternate a and e in lower case.
LC letters here are simply stencil variants of the numbers and letters.
Part of the Stu font family, Stu Mid keeps all lowercases tucked within the x-height space. The character glyphs can be used interchangeably between the various Stu styles to achieve a more "bouncy" typesetting effect.
Stu pays homage to oldstyle numerals, where type designers vary the heights of numbers to resemble a line of running lowercase text. It seeks to address the question: "What if every lowercase alphabet also had varying heights?" The result is a font family with full-fledged ascenders ('Hi'), strictly x-heights ('Mid'), and only descenders ('Lo').
You can view the documentation of the Stu font family design here.
This turned into a whole series when all I was trying to do was simple 3×3 oversized pixel font. One tiny modification to try and fit some glyph into the established structure led other glyphs to conform to the modification. As a general practice, every time I make a modification to a completed glyph, I make a copy of it first. When enough glyphs were conformed to a/the modification, I moved them off to a clone.*
While working on the clone, some new tiny modification would generate glyphs that were similar but enough different that it warranted it's own clone. And so on...so much that the naming scheme had to be changed a few times as well.
And the series is not even all that good. But once an idea hits...and the FontStruction is easy to do... it might as well be "completed". There are 9 versions of tmADHDs at varying states of completion at the time of first sharing.
*This is an over-simplification of the process. What actually happened was that the first iteration ended up with what looked like three similar-yet-distinct styles so I made two clones of the first and deleted glyphs of the first style from the second and moved glyphs to uppercase of the ones that seemed to belong to the second style and added new glyphs to flesh out the style. Did the same for the third. Lots of back and forth between the three iterations to ensure none were left behind or inadvertently deleted. Still there were enough individual glyphs left that I didn't know what to do with. Then I created a fourth clone and moved the left-overs to it. Which later turned to fifth and sixth clone. At some point the thought occurred that tmADHD2 doesn't need to be as wide so it became tmADHD2a and the narrower iteration became tmADHD2b. And so on.