microsoft / cascadia-code

This is a fun, new monospaced font that includes programming ligatures and is designed to enhance the modern look and feel of the Windows Terminal.

Other

25.82k stars 803 forks source link

Distribute Cascadia Code via the Windows Store #39

Open nor0x opened 5 years ago

nor0x commented 5 years ago

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.

PhMajerus commented 5 years ago

Shipping it as a standalone font in the Store would definitely make sense, as it would make it easily available for use in other products instead of being confined to the Windows Terminal app.

SergioMorchon commented 5 years ago

Yeah, this situation is the same as we have with executables: both methods (standalone and through the store) are a nice-to-have. The one requires to keep it updated manually. The other updates it automatically that, as a Windows user, I prefer.

So both strategies would be great

pronichkin commented 5 years ago

Apparently there's a ton of issues when installing fonts manually if certain Windows hardening is enforced with Group Policy.

A by-product of this hardening (if I get the idea) is that nobody can install a font, unless the process is elevated. And since there's no way to elevate Explorer (windows shell), this means even administrators cannot.

Of course there's still a way to do so with command line (as always.) But the command line options for installing fonts seem to be rather obscure, and there's no standard built-in way.

Yes, not all customers are affected by these constraints. But for those who are, I hope that distributing the font thru Windows Store would serve a big relief.

cinnamon-msft commented 5 years ago

We are actively working on this and any updates will be added to this issue! 😊

myokeeh commented 5 years ago

The very first place I looked was the Store.

MattBDev commented 4 years ago

Is there anything holding back a release on the Windows Store? Is it because Windows Terminal hasn't been released yet?

AkazaRenn commented 4 years ago

Is there any updates to it?

ArmandDelessert commented 4 years ago

Hello It has been almost a year since @cinnamon-msft indicated that you are actively working on this issue. What's the status?

Mr1008 commented 3 years ago

Hello, @cinnamon-msft! Do you have any update about this one? Is this still taken into consideration in any roadmap?

Mr1008 commented 3 years ago

I know that currently it is distributed via store with Windows Terminal but it lacks 'PL' version. So as an alternative maybe adding 'PL' version to Windows Terminal would be enough/easier.

brunovieira97 commented 3 years ago

If publishing a font to Windows Store is so difficult, I understand why many apps are not present there.

Doing multiple installations every time an update goes live is problematic, I've ended up with duplicated fonts on Windows Settings. And it's so much work for updating a font, when Windows Store can do that for me!

Any news on this, @cinnamon-msft? A reason for not delivering this?

Edit: I believe the best approach is to separate Cascadia from Windows Terminal. Deliver both through Windows Store and prevent problems such as this one.

alexmyczko commented 1 year ago

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

TPS commented 1 year ago

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

@alexmyczko That doesn't seem relevant for a Microsoft product on their own distribution platform.