by thalamic
Download disabled
The designer of this FontStruction has chosen not to make it available for download from this website by choosing an “All Rights Reserved" license.
Please respect their decision and desist from requesting license changes in the comments.
If you would like to use the FontStruction for a specific project, you may be able to contact the designer directly about obtaining a license.
12 Comments
All the truncated corners, trapping, and the little notches (a, g, w! I, J, T!!) delight me, especially how quite effective they are at pixel size. The pixel display is strong throughout.
Your fluid s, lovely as it is, looks to me slightly too bold and the z too wide. Decent tradeoffs for such fantastic forms, though it may be worthwhile investigating a narrower z.
2334/2334 and a very special top pick indeed! :)
I am waiting for the day someone publishes a website entirely set in fontstructions...that day gets closer every time a gem like this is released.
@meek: Thanks for the Top Pick.
@will.i.om: Appreciate the appreciation. Your kind scrutiny is always a notch above my own and your suggestions always help to make things better. Technically the initial z was the same width as the rest of the characters. I made the E F and L narrower to optically match the rest and I should have done the same for z from the start. I think the problem was I was more focused on maintaining the z diagonal roughly the same angle as the s which caused it to appear wider than the rest. The s is a different story. I must have made seven or eight different s versions before settling on the initial public version. There are two problems with the s that I can't overcome. 1. The x-height, which forces a particular placement of the bricks for it to be rotation-ally symmetric. That makes the s appear either half a brick too thick or half a brick too thin. The current s is the half-a-brick too thin version. 2. The inside curves are achieved using fs2.0 brick stacks. The way I could get them working with the already established curves in the fs was to move the whole glyph half a brick over. While that is fine for sharing purposes, the anal-retentive perfectionist in me finds that mentally annoying. I tried additional brick stacks to move it back half-the-brick, but custom brick refused to be split into two brick combo. I'm attaching an image to clarify what I mean. The s in black is where I want the s to sit and the bricks in red are the ones I can't seem to achieve. Maybe you or someone else can help solve that brick stack mystery. As for the kerning, well...
@intglio: Thanks.
@aphoria: Thanks.
@kix: Thanks. I like the a too. The w turned nice too. x is the weakest glyph, methinks.
@xenophilius: Thanks.
@Frodo: How you managed to spot the missing brick on the é is amazing. Also, thanks.
Somehow the half-brick too thin spine on your currently shared s is a closer optical match than the half-brick too thick version. I am interested to know why this is. Thanks again for sharing it and re-inspiring my investigation of the matter.
I am impressed all over again by how fs 2.[1] allows for such relatively fine adjustments to ‘curves’ and counters formed by complex arrays of polygonal bricks. I also understand quite well how this works. So, my surprise must be relative to just how highly tedious, prior to [stackable] composites, grid-doubling an entire fontstruction used to be as the only way around such tight corners. [Stackable] composites are great as they allow local grid-doubling. So often, it is just one or two exotic characters that might particularly benefit from the increased resolution.
fs 2.[1] proves a versatile solution even in the half-brick shift conundrum posted above. Meaning, this shift is currently possible.
Now, for that x...
Please sign in to comment.