Skip to content
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

Feature Request: Consider making it a Variable Font #90

Closed
mdtauk opened this issue Sep 21, 2019 · 7 comments · Fixed by #304
Closed

Feature Request: Consider making it a Variable Font #90

mdtauk opened this issue Sep 21, 2019 · 7 comments · Fixed by #304

Comments

@mdtauk
Copy link

mdtauk commented Sep 21, 2019

Make Cascadia Code a Variable Font

Additional weights, widths, should be generated by making the font family Variable. This means all glyphs should have the same number of nodes defining the outline, between the light and bold weight axis, as well as between the narrow and wide width axis.

By making the typeface variable, it allows for users to adjust the base weight to aid in readability, whilst allowing for bold text for contextual styling and emphasis, whatever the chosen weight value.

@fearthecowboy
Copy link
Member

Indeed -- the font is quite wide and thick. I do like the shape of the letters, but I find that a the height I like to work with, it's a tad wide.

a 'narrow' flavor (or whatever mystical font-incantations it takes to make it do that) would be very much appreciated.

@be5invis
Copy link

+1 for a narrow “half-width” variant -- Glyphs being exactly 1/2-em wide.

@bitcrazed
Copy link

We hear you and discussed with @aaronbell yesterday. @cinnamon-msft is writing up a plan & roadmap and will share in a week or two, so stay tuned :)

@mdtauk
Copy link
Author

mdtauk commented Oct 3, 2019

When defining a Weight axis, I think the current font would fall into a Semibold, rather than Bold or Normal/Regular/Medium weight.

This is when you actually generate instances. But it would be good for Windows Terminal at least, to support a Weight (and a Width) slider when those axies are present in the chosen font.

@ahmed-alamer
Copy link

A Regular and Retina editions would be great, the font is a bit bold on mac -- both built in and external display (4k) --

@smlombardi
Copy link

smlombardi commented Dec 11, 2019

I like the glyph shapes, but overall it's too "heavy". As others have said, it seems more like "semibold". If I could specify a font-weight of 300, or it its weight was more like that of Fira Code Regular I would be happier with it. This is on a Mac with a 5K display.

@aaronbell
Copy link
Collaborator

@smlombardi Yes, a lighter weight is definitely on the roadmap. This version was aimed to have enough weight to render well at smaller sizes on mid-to-low resolution screens, but it would definitely feel a bit heavy on high-end screens :)

DHowett pushed a commit that referenced this issue Jun 29, 2020
This major update adds a weight range to Cascadia Code. This font is now
being built as a Variable Font, which enables users to select the
perfect weight for their preference. 

The weight range now extends from ExtraLight (200) to Bold (700), with
the current Regular set at 500 (400 in the font selector, 500
internally). As a variable font, OS / rendering engine support may vary.
Users running Windows 10 and Windows Terminal will have access to the
full range of font weights. Other applications may only have access to
the named instances (ExtraLight / Semilight / Light / Regular / SemiBold
/ Bold) depending on inbuilt support. 

Static instance OTFs are also provided. At current, static TTFs are not
built in this update, but it is something we will consider in the
future. 

Variation implementation tested on Windows and Mac, font hinted and
reviewed on high and low DPI devices. 

Closes #25 - weight axis added
Closes #43 - with weight addition, parenthesis width is preserved 
Closes #284 - ligature now broken for easier recognition
Closes #90 - produced as a variable font
Closes #128 - MORE WEIGHTS 
Closes #285 - contextual code removed

Signed-off-by: Aaron Bell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants