[Feature Request] Distribute Cascadia fonts as a Windows component through Windows Update

[levicki]

As the title says, and given the number of Microsoft products using the font (VS Code, Visual Studio, Windows Terminal), and the number of issues with the aforementioned applications (1, 2) I believe it would make sense to make the Cascadia fonts part of the Windows operating system and distribute updates for them through the Windows Update sa part of non-security (i.e. quality) updates.

Alternatively, publish them on Windows Store and have dependent applications automatically install them.

[IllusionMH]

Alternatively, publish them on Windows Store and have dependent applications automatically install them.

This is tracked in #39

[levicki]

@IllusionMH

Alternatively, publish them on Windows Store and have dependent applications automatically install them.

This is tracked in #39

This issue suggests a better option first and Store as a last resort.

Adding the fonts to the new releases of the Windows ISO images as a serviceable component, and making it available as a downloadable KB package for the older Windows installs where once installed they get updated via Windows Update would make the most sense.

The Windows Store distribution doesn't solve the problem for OS versions that don't have the Store preinstalled like the Windows Server or the Windows IoT Enterprise.

[alexmyczko]

https://github.com/microsoft/cascadia-code/issues/220#issuecomment-602872147

[levicki]

#220 (comment)

I don't see the relevance of that comment to this particular feature request.

Windows Server OS is Microsoft's own "distro" so having a way to install Cascadia font there shouldn't be out of scope.