i would say mostly it was luck that it worked out the way it did :) perhaps behind the luck is really the luck of the grid - sometimes good sometimes bad. or either way you make it work the best that you can. but i will post a couple of pics to try so show what's going on.
the o is a central character. the lower right arc is also used as the script connector or whatever the correct name is. i put a box around the area to show both are the same. the next screenshot is the n which shows the placement of the lower connector. both have arrows that show where the connector will hit on the left side. so those are the basics and then you just play around and make it work. also filters are 2:2 and advanced spacing is set to .5.
I like a lot the mix of curved and straight (suggested) segments of this set, that adds some freshness to the dot-based design.
My two cents: I would consider calibrating the letterspacing (maybe shortening some of the connectors) and the width of some glyphs (e.g. the "e" has a wonderful shape but seems wider than most the other glyphs).
thank you meek, once again for the tp. always nice to get and always appreciated.
@em42 - thanks for your remarks and suggestions. i ended up shortening most of the connectors and thus tightening the script. also, although i was kinda digging the fatter e, your suggestion works fine. both are improvements and thanks again.
thanks elmo, upixi and lady :) i imagine i will add the uc, but sometimes i think the innocence of a set can be lost by adding uc. these are playful characters so the challenge would be to make the uc even for fanciful. i'll think about it...
Meek, cloning is not working for me. i tested this file and although the cloned file shows the characters, it doesn't show glyph count. i haven't checked to see if the file actually works. i think it does, but will check that also. without any glyph count it appears fontstruct will not really publish the font although it appear it has, but it never shows in the live stream. usually it's a matter of seconds before a font appears there. has anyone else had any problems with cloning? maybe it's just my files or certain ones.
A lovely font, somehow it reminds me of the cotton wool balls I threaded on knitting yarn to use as garlands in trees and bushes for summer birthdays. Really cheerful. 10/10
19 Comments
i would say mostly it was luck that it worked out the way it did :) perhaps behind the luck is really the luck of the grid - sometimes good sometimes bad. or either way you make it work the best that you can. but i will post a couple of pics to try so show what's going on.
My two cents: I would consider calibrating the letterspacing (maybe shortening some of the connectors) and the width of some glyphs (e.g. the "e" has a wonderful shape but seems wider than most the other glyphs).
Anyway, a very nice design!
@em42 - thanks for your remarks and suggestions. i ended up shortening most of the connectors and thus tightening the script. also, although i was kinda digging the fatter e, your suggestion works fine. both are improvements and thanks again.
http://www.youtube.com/watch?v=N-uyWAe0NhQ
how do i favorite a font? i found how to rate them, and how to d/l, but not how to favorite.
Meek, cloning is not working for me. i tested this file and although the cloned file shows the characters, it doesn't show glyph count. i haven't checked to see if the file actually works. i think it does, but will check that also. without any glyph count it appears fontstruct will not really publish the font although it appear it has, but it never shows in the live stream. usually it's a matter of seconds before a font appears there. has anyone else had any problems with cloning? maybe it's just my files or certain ones.
@funk_king It’s just the glyph count. It’s a bug and will be fixed in the next update.
cool. thanks.
A lovely font, somehow it reminds me of the cotton wool balls I threaded on knitting yarn to use as garlands in trees and bushes for summer birthdays. Really cheerful. 10/10
j'ai besoin de coeur pour faire battre le mien
Please sign in to comment.