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.
14 Comments
You've really been on a tear lately.
Madness: repeating the same behaviour in the expectation of achieving a different outcome.
I'd rather that than experience too much more of the unable-to-save glitch. Anything but that!
Good job I made a screen capture of the punctuation before I exited. I just had an inkling... the minisaves weren't working...
Sorry if you had some saving problems. The server is ok at the moment. Should be better than ever in fact.
Problems with saving do occasionally arise with very large FontStructions like this one. We will continue to work to try and improve this. Let me know if this particular problem persists.
Great work by the way!
Go!
;)
I also have some technical issues with Fontstruct: I simply can't open and edit one of my fonts, and some large fonts are displayed only for a few seconds.
It's what I admire about some of the top-notch designs I see being released here. Beautifully thought-out and executed alphabets that follow the canon, yet have personality.
@frodo7: thanks, I must say I was pleased myself with the l/c a and the g. A tight double-bowl at this weight and with such severe curve-cuts is always a dodgy proposition.
Attempting to rise to your challenge (through gritted teeth) I'm working on this little number.
I've taken a lot more care than I usually do to make sure everything is as tidy as I can make it (where the bricks fall on the grid, widths, etc) and so far, touch forehead, everything seems just so -- with the exception of the s which falls victim to the over-generous "curve" segments.
Ive done it on a truly gargantuan scale which I hope is not going to be a file-size problem later on. I've done so because if I decide to strike a reg,bold and black, (hah hah! he's dreaming!) I need plenty of headroom in what will become tight intersects to pull it off.
Comments welcomed (from anyone else too). I shall listen very nicely and then try not to go out and do precisely what I want.
p.s. I realize the spacing is a little off. No point finessing it until I've got the dreaded upper case done.
As for the s: usually I tighten the bowls for letters with stems like b,p,d etc. This time I've got the same thing going over the whole lot, which adds a certain overall look. If you think it's ok to tighten up just the s I'll try that. I guess what's important is maintaining a balance between "look" and obedience to the mechanics of construction. That's where the art is, n'est?
As for a bold... !! We'll see if I can master my impatience with doing the same stuff twice, shall we! Not that it is, of course. It might as well be a completely different beast. All the sweat and work with only the (to me!) tiny advantage of extended usefulness. Ugh.
I might ditch the "seriflets", too. I know they'll give me grief. What do you think?
(someone should probably write a thesis about fontstructors psychology. :P)
very nice font, great readability... but the thing that got me really exited here is that screenshot of your "standard" font... can't wait until you release this beauty!
may i suggest Exempla to the standard font competition? ;) (maybe it should lose some weight and grow some serifs though...)
I fully intended to rise to thalamic's challenge of a completely quirkless, standard font. But I started out wrong by using diagonals for the A, Vv, Ww, etc. Eventually I'll press on with a ruthlessly rational version but in the meantime I'm fed up with it. (It bores me.) Meanwhile this one is full of the usual intagliana, for better or worse. It's a hairline and I'm trying to strike a light and a regular off it, but I'll probably run out of steam long before I get to a bold.
Ooops! Spelling mistrake in the sampler. No l/c x.
Please sign in to comment.