-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More open “5”, “c” and “e” #1287
Comments
Mimicking humanist sans-serif is considered out of scope. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days. |
Built Iosevka with [.widths.normal] "shape = 610", and [.metric-override] "cap", "ascender", "xHeight" and "parenSize" scaled down by 0.90 (10% shorter glyph size) to make glyph size close to Source Code Pro. Font size 12 for example: And, yeah, in this case I would agree with @twhb - more open "c" would be good, but not as open, as @twhb pictured. Just a little bit. MsPaint "simulation": |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days. |
I'm still interested in a more open |
I support more open |
My concern: Having a more open aperture (or, "separation between strokes") is a feature of humanist sans-serif. |
But if it worsens the readability of glyphs... Perhaps there is a compromise solution? What criteria are used to define the size of the separation? Just wonder. |
I don't know if this carries any weight, but some fonts considered neo-grotesque but with especially open |
OCR-B is also considered neo-grotesque and it has an aggressively open 5: I think the problem with Iosevka here is that it attempts to make the curved corners in the loop of the 5 almost symmetric (left side being a mirror of the right side), which results in an excessively closed angle where the curve touches the vertical stroke on the left, and a tail that curls up too much. |
Did a little experiment on using completely flat hooks on either end, kinda copying FairfaxHD and a few other pixel-based fonts I suppose it would be a compromise between staying geometric and having an open aperture, though the results looks kinda meh: Having a flat top but a curled bottom makes the shape look more like a G, while the others look sorta fine in Heavy but gradually looking out-of-place in the thinner weights (especially Classical + Flat). The Flat+Flat combination looks like it would go along with variants like #1269, but it also feels like a completely different style at that point. I'll just leave this here for visualization/reference; I don't strongly recommend these takes. |
Flat+flat might look better wit a larger curvature radius on the other side, but that might make the c not fit in the style of other characters. |
I just copy-pasted a bunch of Iosevka I think something between |
afaik (and to answer @susinodan's question) Here's what happens if I replace it with Which does look more open, but not without its own issue: |
Issue aside, I think it looks much better that way! What do others think? |
Just to add my 2 cents. As mentioned by @vladkryv, the legibility of A more open P.S. Thank you very much @be5invis (and contributors) for this amazing font! |
There might be two sub-variants:
May need to be careful about the GID impact -- we have over 40K glyphs now again. |
@be5invis thank you for your work. I'd like to ask a couple of clarifying questions about the proposed sub-variants:
|
It will affect other glyphs (unless something is changed), like
See this for a very rough demonstration for But otherwise, here are some other fonts without hooks as reference: |
Having the bottom left of the “5” curl less upward makes it more distinct from a “6”, especially at small sizes, while still being recognizable. Similarly, having “c” a bit less closed makes it more distinct from “o” while still being recognizable. A more open variant is already available for “g” (and appreciated), and a somewhat similarly edited variant for “t”.
The text was updated successfully, but these errors were encountered: