Curvilino

Share:
by fontcollector

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.

This font is an experiment using filters set at vertical 2 and horizontal 1. Any comments and suggestions for improvement are welcome!
Info Created on 21st September 2011 . Last edited on 25th October 2011.
License Creative Commons
Categories
Tags
Fave Tags

22 Comments

Very nice. 10/10
Comment by Mario jr. 23rd September 2011
Cool font, I've been looking all over for a font as narrow as this
it doesn't have to be monospaced though
Comment by Scott Calo (truth14ful) 23rd September 2011
@Mario jr.: Thank you!
Comment by fontcollector 24th September 2011
@truth14ful: I'm happy you like my latest work!

Although a large number of these glyphs are the same width, the Curvilino font isn't monospaced; for example, compare the @ sign with the exclamation point.

I appreciate your kind remarks!
Comment by fontcollector 24th September 2011
A good looking design.10/10

If I may make a couple of minor points Dan, I would have the crossbars of the 'f' and 't' a wee bit shorter. (in the sample text look at the 'fo' of fox and the 'tz' of quartz).

I would also make the 'AE', 'ae', 'OE' and 'oe' ligatures share a central horizontal, so that they don't look so heavy.

Minor points on such a good design :)
Comment by p2pnut 24th September 2011
@p2pnut: You know I always appreciate your suggestions, Ray!

I have struggled constantly with the problem of the f crossbar. If I make it shorter, then there will be a huge gap separating it from any letter without an ascender. The issue is less critical with the t, since its curved base takes care of that spacing issue. Even so, I have used the longer crossbar for both glyphs merely for consistency. I'm going to fix the t, because there's really no good reason for it to match the f.

As for the AE, ae, OE and oe ligatures, you're exactly right. My original AE and OE overlapped in the center as you advise. It's just impossible, however, to achieve the same result with ae and oe, because of the 2 by 1 filter settings. Believe me, I tried over and over to resolve this conundrum, but the macaroni bricks at the top of each single letter simply will not line up with a shared central line! Although I can and will return AE and OE to their prior ligature patterns, I can't find a way to fix ae and oe. So I'm left, as I see it, with two choices: either ae and oe must remain as they are, or I can delete them. At the moment, I'm leaning toward the latter solution. Please let me know what you think, and thanks again for your remarks!
Comment by fontcollector 24th September 2011
@p2pnut: Ray, please take a look at the image shown below. It illustrates the situation I described regarding both ae and oe. You'll see that the macaroni bricks can't be aligned with a single central horizontal line. If the filters weren't set at 2 by 1, I wouldn't have this problem; that's why I've decided to eliminate these ligatures. It may be like sweeping them under the rug, so to speak, but there you have it! :)
Comment by fontcollector 24th September 2011
Possibilities. No overlaps. 5 composite bricks.
Comment by thalamic 24th September 2011
@thalamic: Why didn't I try making composite bricks? I've used the brick-stacking technique many times, but I never thought about composites until you showed me how to solve the ae and oe issue.

Thanks so much, Ata!
Comment by fontcollector 24th September 2011
I must confess that I hadn't taken the 2:1 filters into account ... I have tended to steer clear of such complications ... luckily others (like thalamic) have boldy gone where I fear to tread :)

As for the problem with the 'f' (this also is useful for 't' and 'r'), all you have to do is move the Letter Space in a bit (I believe this is called 'negative kerning'). below is an example from one of my old designs ...
Comment by p2pnut 25th September 2011
@p2pnut: Thanks again for spending so much time trying to improve my glyphs, Ray!

I've tested several possible solutions for the crossbar of the f. In each of the three images shown below, figure 1 shows the crossbar at its original 2-brick length; figure 2 uses the shortest crossbar (1/2 brick); in figure 3, the bar is a bit longer (1 brick); figure 4 features the shortest crossbar again, but with negative kerning of a single brick; and figure 5 employs a new composite 3/4 brick.

First, let's rule out figure 1, the original f, in all three cases.

Example A [“fox”]: In figures 2 and 3, the gap after the f is unacceptably wide.

Example B [“fur”]: Again, in figure 2, the gap's width is excessive. Figure 3 is a little better, but still not ideal.

Example C [“fly”]: Figure 2 is fair. Figure 3 works reasonably well. But in figure 4 (negative kerning), the f and l are actually touching!

I believe, therefore, that the best compromise for all three situations is figure 5, using the 3/4 brick crossbar, which I manufactured after reading thalamic's advice regarding composites.

And now I'm completely exhausted! :)
Comment by fontcollector 25th September 2011
Comment by fontcollector 25th September 2011
Comment by fontcollector 25th September 2011
Comment by fontcollector 25th September 2011
Its worth all the effort though :)

I think C/3 is looking good.

One thing I noticed is that ascender of the 'l' has that small 'return' at the top (I'm afraid I don't know the technical term).

A) It is not found in any of the other ascenders.

B) Without it you might be able to space the 'f' a wee bit tighter.

Just a thought.
Comment by p2pnut 25th September 2011
@p2pnut: Yes, C/3 is satisfactory; yet number 3 doesn't work nearly as well in situations A and B. Since I must choose one solution that looks good in all three cases, I still think figure 5 is my best option.

As for the serif at the top of the l, it's there to make sure this glyph isn't interpreted as a 1, which has a different type of topper. I know the other tall ascenders are topless; however, both the i and j have the same serif as the l. I used the serif on the i for spacing purposes, especially when the i is accented. And since the i got a serif, I thought the j should have one as well. :)
Comment by fontcollector 25th September 2011
@p2pnut: After a couple of days away from Curvilino, I've found some new solutions for f, r and t. They're very skinny, but spacing works quite well for all three glyphs in every situation I tested.

I've also removed the serif from the l as you recommended. Spacing remains problematical, however, if i and j lose their serifs, so I've left them as before.

I hope you approve of these revisions. :)
Comment by fontcollector 27th September 2011
Nice work Dan - they work really well for me :)

I prefer the 'l' and it will always stand apart from the '1' because the latter is so destinctive.
Comment by p2pnut 27th September 2011
I have my own set of AE and OE ligatures:
Comment by Scott Calo (truth14ful) 27th September 2011
Comment by Scott Calo (truth14ful) 27th September 2011
@p2pnut: Thanks, Ray! I'm happy you like the latest changes.
Comment by fontcollector 28th September 2011
@truth14ful: It's so nice of you to show me how you've handled your AE, ae, OE and oe ligatures!

I really like the fact that your ae and oe don't rely on the distorted double curves used in my current designs. On the other hand, I prefer to maintain the rounded inner corners of these ligatures. This could be achieved by stacking the composite double curves on top of your solutions. But I've been unable to produce a pair of central notches in order to emphasize that individual glyphs have been joined. This is because of the 2:1 filter settings. I'm going to think about the advantages of your method, as well as the liabilities.

My AE and OE don't present the same problem, since stacking creates the inner curves of both A and O; therefore, I'm going to leave them as they are.

Thank you again for your suggestions!
Comment by fontcollector 28th September 2011

Advertisements