This%20FontStruction%20was%20selected%20by%20FontStruct%20staff.
by chr.s
Details |
Discussion |
 |
Beautiful g and &.
 |
It's well on it's way ... I also love the g and &. Not sure about the bits eaten out of the ascenders.
 |
I going to add that little nice detail in the q to my favorite list.
|
And I AM starting to read my comments before posting embarassing typos...
 |
This is very nice. Kinda quirky, and distinctive. Looks decayed, and Victorian/Parisian with it's curves.
I always think sets deserve an upper case where possible, and I think your numbers need to be a little taller.
8 looks a bit twisted. q could do with a slightly longer stem (although it's still one of my fav's) and not sure about the tail at the end of the 'w'.
 |
Very smooth and organic. Fimbriae successfully hides its humble brick origin. 10/10
 |
Thanks everyone - some interesting comments...
Oddly enough the 'g' was one of the ones I struggle/struggled with most - it had the right personality but never really seemed to fit in my opinion, but maybe I can learn to love it.
Your description is spot on Nippa - and I'll definitely be adding the uppercase at some point - but I wanted to try and resolve the lowercase first, with the view that it might make the uppercase characters more easily settled upon. The slightly stumpy number-height was a consideration and since you point it out, I may well increase it - probably after I've finished the capitals though. You were right about the 'q', but I'm not sure about the '8' - I wanted it to somehow mirror the construction of the 'g' - if that makes sense. And with regards the tail on the 'w', I'm far from decided on that one - it seemed to need a little embellishment to bring it in line with the other characters, but maybe not in that way.
I've also made the crests in the ascenders a little more subtle. This was one of those fonts that continually changed from its original direction and the crests were one of the last remaining details, which I'm too attached to I'm afraid - but I think the newer ones are better.
I think it's getting there, so thanks for all the input so far.
 |
Congratulations! FontStruct Staff have deemed your FontStruction worthy of special mention. “Fimbriae” is now a Top Pick.
|
Wow, the upper case begins. How exciting, as it's looking really cool.
Feelin the new sexier cuts in the ascenders. A great improvement.
|
My reservations about the ascenders have now vanished :) and the U/C shows such promise.
|
Thanks to everyone for the great comments - they really do mean a lot.
However, I'd almost finished the first half of the uppercase when I decided to see how it looked in public preview - most things seemed to be OK as far as I was concerned until I clicked again on 'edit'. Now whenever the fontstructor tries to load Fimbriae, it causes some kind of glitch and I'm left looking at a dark grey screen. I don't know if maybe cloning it would mean I could continue with a copy, but I'd rather not do that. Has anyone else had this kind of error before and come up with a solution?
Help!
|
Ouch! That's frustrating ... to say the least. Sorry, but I haven't experienced this, so have no advice to offer. I wish you well with it.
 |
Try completely clearing your browser’s cache. If that doesn’t work (or if you don’t want to) try another browser (Firefox, Safari, Opera, etc.), open, save, and you should be good to go. : )
|
Thanks for the advice will.i.ૐ but I'm afraid that didn't work for me - it's definitely a problem with Fontstrust itself.
Cloning it sort of worked, in that it would open the application, but there were too many glitches and oddities to make editing a possibility... I may have inadvertently 'circuit-bent' fontstruct.
I think it's going to have to be a case of copying each character into a new 'struction; which may not happen for a while. Oh well, such is the nature of the digital realm.
|
Yes I've had the same error. It doesn't seem to be permanent though. It only happens if I've got too much other stuff opened. Simply shut off you comp, and reboot. Opening just Fontstruct.
It's almost as bad as the 'terror brick' - which when you delete a certain brick, then it won't let you save. That brick, if moved, tweaked or deleted will stop you saving. It usually happens when the memory in Fontstruct starts to dwindle.
|
Space on 'f' needs closing a bit.
|
chr.s, I've forwarded this case to Rob. Fingers crossed!
 |
When I had these problems – FS wouldn’t work for me in Firefox on Mac OS X – I simply took it out of the browser environment. I’m successfully running FS in Prism by Mozilla as a standalone application ever since.
I can only recommend this.
