I've been trying out Cascadia (top one below) but the huge sidebearings around "m" drive me nuts for some reason every time I see a word like "comments" ☹️

Just seems like a huge departure from most monospaced fonts!

from @mdtauk

Description of the new feature/enhancement (with images if possible)

The number "1" is hard to distinguish due to its first stroke is almost horizontal. It looks really like "l" rendered by other font.

This issue could be more obvious when using low-density screens.

Proposed technical implementation details (optional)

Please increase the slope of the first stroke, like so many other fonts did:(below is Menlo)

Environment

Cascadia Code version number: 1909.16
Application (with version) used to display text: Notepad++ v 7.2.2
OS platform and version: Windows 10 64bi Pro 1903 build 18975 (Insider Preview) and 18362
Screen resolution (i.e. 220dpi): 

Any other software?

Steps to reproduce

Copy or enter a spanish special character (áéíóúÁÉÍÓÚÜüñÑ) in Notepad++
Instead of showing the special Character it displays a rectangular box placeholder character

Expected behavior

Characters should display correctly.

Actual behavior

Characters are not shown, rectangular placeholder is inserted instead

Comparison in Notepad++ and Windows Notepad

Environment

Application (with version) used to display text: Word 365
OS platform and version: Windows 10 1903 Enterprise

Issue

Letters Æ, Ø, and Å must be styled to match AE, O, and A respectively.
For example, compare with these letters from Consolas:

Word font menu

Also, rendering of Cascadia's font example in the dropdown in Word is very poor:

from @mdtauk

Description of the new feature/enhancement (with images if possible)

Please add glyphs for accented characters (specifically, for my case, ISO-8859-1-equivalent; i.e.,
U+00C0 to U+00FF); the Greek alphabet, uppercase and lower (U+0370-03FF); and the copyright and trademark symbols (U+00A9 and U+2122).

I have more than a few filenames which contain the first; a considerable amount of mathematical code which makes use of Greek symbols in variable and function names; and, of course, copyright and trademark symbols appear repeatedly in comments and embedded messages.

I add support for homebrew cask.

This is commit link

install command:

brew tap homebrew/cask-fonts 
brew cask install font-cascadia

Cascadia glyph outlines look "rough" in Outlook's font preview ...

... and in Visual Studio

It'd be great if Cascadia could be hinted to eliminate these issues.

I think I've looked at every file in the repo, and I don't see any documentation of what ligatures exist. I'd like to know what all I'm able to use. ^_^

I have installed Cascadia from Github here and in Visual Studio Code the ligatures seem to be working as expected.

In Windows Terminal though, some of them aren't working.
More in particular I have tested these: -> <- >= =>

Environment

Cascadia Code version number: 1909.16
Application (with version) used to display text: pyCharm
OS platform and version: windows 10, 18362.356
Screen resolution (i.e. 220dpi): multiple screens, 4k on 27" and FullHD 15"

Any other software? Issue not present in Notepad++ (but that editor does not display combined glyphs (e.g. !=) correctly so it may be irrelevant.

See attached images, anything right of ( gets pushed a few pixels when ( is highlighted. Same is true for [ and {

The m feels very crushed and narrow. There is little that can be done to fix this, unless every other character is made wider to allow it to breathe.

from @mdtauk

Environment

Cascadia Code version number: 1909.16
Application (with version) used to display text: PowerShell Core Terminal, Command Prompt
OS platform and version: Win10 Pro 1908 build 18363.356
Screen resolution (i.e. 220dpi): 1920*1080 15.6" 125% 

Any other software? Flutter SDK

Steps to reproduce

• Run PowerShell Core terminal/Command Prompt from context menu
• Change font to Cascadia Code
• Run flutter doctor

Expected behavior

With Fira Code

Actual behavior

With Cascadia code

on PowerShell

on Command Prompt

Missing glyphs can be seen above as empty boxes

Description of the new feature/enhancement (with images if possible)

I just changed my font to Cascadia Code on VS 2017 and it looks very feeble compared to Consalas which I have been using forever.

I would prefer it to be stronger than it exists now👍

The horizontal strokes on the tops of Z, F, E, T are 190.0 units thick. On 7 it's 196.0 and on 5 it's 186.0.

At 12pt on a 96.0 DPI display (100% scaling), this results in a stroke with an unpleasantly high optical weight.

(note: this repro image is 6pt on a 196.0-dpi display; it should act similar)

Source: raw glyphs - not a hinting issue

oh-my-posh is a popular and nice prompt for PowerShell, but it requires a font that supports glyphs that don't seem to be present in Cascadia Code right now. Would be great if those could be added.

I know this is done to make the ascender of the f more visible, but it feels a tad too low.

from @mdtauk

The entire range of box drawing (U+2500 - U+257F) and block element (U+2580 - U+259F) characters is not covered by the font.

As of now the /> tag looks like this

Same issue with Fira Code Retina font.

It looks unbalanced. Can you please fix this?

Environment

Cascadia Code version number:
Application: Fontbook
OS platform and version: MacOS Mojave 10.14.6
Screen resolution (i.e. 220dpi): 2880 x 1800

Any other software?

Steps to reproduce

Download the ttf from current master. Try to install using fontbook.

Expected behavior

Installation should proceed without warning

Actual behavior

User is presented with minor warning found during validation

Environment

Cascadia Code version number: 1909.16
Application (with version) used to display text: Gnome Fonts 3.28.0-1
OS platform and version: Ubuntu 18.04
Screen resolution (i.e. 220dpi): N/A

Any other software?

Steps to reproduce

1. Download the ttf file from release
2. Open the file in Fonts
3. Click Install button

Expected behavior

Font should be installed, button should show "Installed"

Actual behavior

Font failed to install, button shows "Install Failed"

Environment

Cascadia Code version number: 1909.16
Application (with version) used to display text: Windows Notepad
OS platform and version: Windows 10 64bi Pro 1903 build 18975 (Insider Preview) and 18362
Screen resolution (i.e. 220dpi): 

Any text editors to be honest

Steps to reproduce

Use any Spanish special characters (and I assume any other language's special characters)

áéíóú ÁÉÍÓÚ üÚ ñÑ

Expected behavior

Font should behave as monospace (same width for every character) This does not happen with special characters

Actual behavior

Character width is smaller than expected.

Note

Probably related to: #52 and #49

https://devblogs.microsoft.com/commandline/cascadia-code/ says

👉 Note: There is currently no proper testing framework built into the repository, so all pull requests will have to be manually tested and validated. This will slow down pull request approvals, so please bear with us. 😊

The www.GitHub.com/googlefonts/FontBakery font testing tool may be suitable for meeting this need. It has been successfully used via Travis CI to do regression testing.

cc @felipesanches @graphicore @m4rc1e

12pt 96dpi

Environment

Cascadia Code version number: 1909.16
Application (with version) used to display text: Sublime Text 3.2.1 Build 3207
OS platform and version: Linux (...whatever version you get by default in ChromeOS linux containers)
Screen resolution (i.e. 220dpi): Don't know, but this isn't hinting related so I don't think it matters.

Steps to reproduce

Type <!-- into a text document.

Expected behavior

Cool html-comment-start ligature appears.

Actual behavior

Ligature appears, but almost all of the < part is clipped. See screenshot:

This happens regardless of where in the line the <!-- appears.

The top curves of "s", "c" and "a" seem vertically compressed.

As a result the x-height of the words formed by these letters don't look balanced.

The lack of character on the top stroke of the number 1 feels out of keeping with the shape on the lowercase c and the stylised 2. Now the bottom stroke of the lowercase l is curved, it is distinct enough from the number 1 to allow for a diagonal top stroke.

from @mdtauk

12pt 96dpi -- not a hinting problem, reproduces at all scales

In my opinion, it's better to use straight lines for the lowercase letter "k"

The lowercase r's serifs make it feel out of character to the other lettershapes.

from @mdtauk

Environment

Cascadia Code version number: 1909.16
Application (with version) used to display text: Visual Studio 2017, Word 2013
OS platform and version: Windows 10, 16299.1387
Screen resolution (i.e. 220dpi): 1920x1080

Any other software?

# Steps to reproduce

Simple comparison of fonts side by side in Word will show.

I typed a few copies of the same character out on 1 line in Word, then repeated it with another character on the next line, like this:
  TTT
  AAA
  ZZZ
I then set the first character per line to 10pt Calibri, the 2nd to 10pt Consolas, and the 3rd to 10pt Cascadia Code.  Cascadia was noticeably taller:
![FontSizes](https://user-images.githubusercontent.com/36713063/65252188-874f1f00-dac6-11e9-867b-53e5ebc975ea.png)

I then set the first 2 characters to 11pt and they appeared as the same height as the Cascadia character:
![FontSizes2](https://user-images.githubusercontent.com/36713063/65252346-ce3d1480-dac6-11e9-9afa-aa1f18d2358a.png)

# Expected behavior

Characters should be the same size as other fonts.

# Actual behavior

Cascadia Code appears to be 1pt larger than other fonts of the same size (Calibri and Consolas at least).

Description of the new feature/enhancement

Since there is a font section in the Windows Store, wouldn't it make sense to distribute the font there? Especially if it gets updated regularly? Would be a useful addition for developers on Windows.

BTW great work, i installed Cascadia Code on all my dev boxes already.

An officially-maintained Chocolatey package for the font would be great to have (à la https://chocolatey.org/packages/FiraCode-ttf).

The distinction between "=" and "==" is quite subtle which could be dangerous for c++ code, maybe a 3 line equals for the "==" ligature could be more appropriate?

Until the font and its design makes its way to GitHub, I wanted to offer a couple of thoughts on where the font stands so far.

a

I think the lowercase a feels heavy and awkward.

f

I think the bar on the lowercase f feels too low (I know this is done to make the ascender of the f more visible, but it feels a tad too low.

r

The lowercase r's serifs make it feel out of character to the other lettershapes.

m

The m feels very crushed and narrow. There is little that can be done to fix this, unless every other character is made wider to allow it to breathe.

1

The lack of character on the top stroke of the number 1 feels out of keeping with the shape on the lowercase c and the stylised 2. Now the bottom stroke of the lowercase l is curved, it is distinct enough from the number 1 to allow for a diagonal top stroke.

Other ideas

There could also be vertically centred punctuation when used between Uppercase or Lowercase letters or numbers.

There could be oldstyle and tabular digits used contextually.

There could be special digits used for line numbers.

If the font was a variable font, the regular and bold thickness could adapt when the text is dark on light, or light on dark.

Error messages could also appear bolder than the standard regular and bold weights.

Is it possible to make the font compatible with Chinese characters?

Getting an Error when installing the Font on a Mac

The LICENSE file on line 2 specifies a Reserved Font Name, but this means anyone forking the repo and making a change, without first changing the name, has their license terminated. This is very serious!

Please either remove the RFN (my recommendation) or change the font family name in the source files to another codename.

this prevents the use of the font in applications that are very "strictly" monospaced, as the font is not considered monospace (I can't use it in gvim without fixing the advance on that glyph to 600)

In this font, ->should be replaced with a right arrow. But in visual studio 2015, it's not.

Tried switching to CC in VS Code on macOS, from my previous font of SFMono-Regular, by installing the .ttf into Font Book, and putting 'Cascadia Code' at the beginning of the Font Family box in VS Code.

To my eyes, the font is a bit heavier than what I'd prefer. It seems as though only one weight was installed, "Regular," is that right? If so, any plans to provide lighter weights to choose from?

The bottom corner of the "y" looked a bit unfinished - sort of like a "v" that accidentally got a descender.

from @mdtauk

Environment

Cascadia Code version number: version used in Sept 19 2019 blog post
Application (with version) used to display text: Mac Firefox 69 and Chrome 76
OS platform and version: MacOSX 10.13.6
Screen resolution (i.e. 220dpi): 220dpi

Steps to reproduce

1. Load the blog post https://devblogs.microsoft.com/commandline/cascadia-code/
2. Look closely at the first subhead (“Wait, what’s Cascadia Code?”)
3. Note how the baseline of the ‘W’ and ‘w’ characters fit with the rest of the line

Expected behavior

The baseline of the Ws should match the surrounding characters (particularly the ‘i’ and ‘h’)

Actual behavior

The baseline of the Ws appears to be a pixel too low.

Environment

Cascadia Code version number: 1909.16
Application (with version) used to display text: Windows Terminal 0.4.2382.0
OS platform and version: Windows 10, Insider build 18980

Steps to reproduce

1. Open Windows Terminal.
2. Switch the font in use to Cascadia Code in the Settings.
3. Run a program which displays lines drawn with box-drawing glyphs (for example, pstree).

Expected behavior

Drawn lines should be continuous.

Actual behavior

This shows the result of switching Windows Terminal to Cascadia Code 10, having previously been using Consolas 10, with which font the lines in the directory tree and at the right of the prompt do appear continuous. As can be seen, this is not the case with Cascadia.

Like this

and this in my QtCreator

Its not easy to see when the font is small

Can you please improve it?

Description of the new feature/enhancement

Currently, I’m using Input Mono Narrow, which is the version of Input Mono that is metrically-compatible with Consolas.

Cascadia Code is ever so slightly thinner than Consolas, which makes long lines of code to be shorter than when Consolas is used, which is what I used previously, as it’s the built‑in monotype font on Windows.

I have just tested this font and found that the accented letters are rendered lighter and smaller or as empty box. See cascadia-example.tar.gz.

The cascadia-emacs example shows òàploiç... in which ploi are right but see the others.. Instead the cascadia-dos example shows an empty box in place of an à

Thanks