"y" looks "a bit unfinished" about cascadia-code HOT 10 CLOSED

It’s a style in typography; it’s not a bug.

Like Chagall paintings, it may be a form of art, but I don't want it in my home.

but srsly at some point there will need too be some form of guidelines as to (who/) how a decision is made about some visual design.. e.g. my issue is with the "4" (#66) that is mostly a design issue I have with it, not a technical one.
While I think the y looks ok when small, increasing the font size for presentations makes this visible and once you see it, you cannot unsee it.

from cascadia-code.

I’m fairly sure, but I can’t find the original source. You also remarked on the side bearings on the m/M in the same source comment. Maybe it was on Twitter?

Hmm, @bitcrazed transferred over the thread I started in the Terminal repo #74 which has the comments about the narrow and crushed m...

And I can only see three tweets with Cascadia mentioned.

Eitherway I don't think the y looks like a V with an accidental descender, the cut out is both an ink trap, and a character quirk for the glyph so consider this closed, if it was a comment I made.

from cascadia-code.

Ink traps are relevant for printing, particularly small text on low-quality paper, not displaying on a screen, right? All of the example of ink traps I see on the Wikipedia page look bad in a way that I think is hard to argue with (but would look good in print due to ink spreading, as that's their whole point).

I agree that this isn't very noticeable at standard code sizes (tho now that I know about I'm seeing it normally, ugh) but would be very noticeably when blown up. It definitely looks like a v with a descender attached.

This might be more related to the request for a "Display" variant of the font (#91), tho; I'd definitely expect a Display variant to not contain any ink traps, at least.

from cascadia-code.

but I can understand how you don't enjoy it.

Give me a month of getting used to it 😅. I don't have any hard feelings about it.

I mostly only wanted to bring up how decisions are made according to style. For example, the 4 glyph follows american/british handwriting that is unnatural to other parts of the world. Other decisions, like this issue being discussed, is purely a decision of tase. This being an open source project by design, it is hard to reach a decision without guidelines. E.g. is it ok to follow styles that mostly Americans are used to (4) or have design decision with community input. I mean I can't possibly create a sensible unit test that reproduces a bug or anything 🤣

from cascadia-code.

It’s a style in typography; it’s not a bug.

from cascadia-code.

Was that a comment I made?

from cascadia-code.

I’m fairly sure, but I can’t find the original source. You also remarked on the side bearings on the m/M in the same source comment. Maybe it was on Twitter?

from cascadia-code.

The Ink Traps also help with hinting, to keep edges crisper.

from cascadia-code.

@tabatkins Ink traps are just as useful on screen as they are in print—perhaps there isn't ink spread, but too much weight can result in more, darker pixels. By building in ink traps one is able to actually reduce the darkness of pixels at key spots in a letterform and enable more even color to the letterforms.

@dasMulli Cascadia Code, at present, is definitely designed for small scale use, so some of the design features designed to help reduce weight, or better fill the space, are really only intended for smaller sizes. I would argue that the /y isn't a totally unusual design feature (I've seen it on many other letters) but I can understand how you don't enjoy it.

from cascadia-code.

Give me a month of getting used to it

Sadly that doesn't work for me @dasMulli, i tried to ignore it but it is too distracting. I will be reverting to the Consolas.

from cascadia-code.