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

Windows 10 doesn't register it as monospace type? #4

Closed
otterpro opened this issue Jan 15, 2020 · 13 comments
Closed

Windows 10 doesn't register it as monospace type? #4

otterpro opened this issue Jan 15, 2020 · 13 comments
Labels
bug Something isn't working

Comments

@otterpro
Copy link

On my Windows 10 setup, it seems to be registering as a proportional and not monospaced type. For that reason, it won't show up as available font in Command Prompt or Powershell. Other fonts like Fira Code or Inconsolata are fine.

@philippnurullin
Copy link
Member

We aware if this problem, one of the weights is missing "monospace" tag in metadata. This will be fixed in next update.
Thanks for feedback.

@damieng
Copy link

damieng commented Jan 17, 2020

I think this might actually be a lack of Panose flags set - that's what Windows Command Prompt uses to identify monospaced fonts. While it was included in FontLab Studio 5 it did not make FontLab 6 or 7.

A separate process/patcher might be required to fix up the ttf after processing. Here's what it looks like in FontLab Studio 5. Toggling this flag is the difference between it showing up in Command Prompt options or not although toggling it does not affect Visual Studio for example.

image

@atsusta
Copy link

atsusta commented Jan 17, 2020

I use gVim and it loads monospaced fonts only. same here like cmd or powershell.

@AndreyKozhevnikov
Copy link

Hello. Is there any time frame for this update?

@philippnurullin
Copy link
Member

if stars will be merciful, the v 1.0.1 will be up in next 8 hours.

@philippnurullin philippnurullin added the bug Something isn't working label Jan 17, 2020
@philippnurullin
Copy link
Member

The stars was not so merciful, but we fond the solution. Expect 1.0.1 in Monday. Sorry for the wait.

@neshanjo
Copy link

Thanks for fixing! Now we can have JetBrains Mono in Windows Command Line, too! 😄

image

See e.g. this post on how to add fonts to the windows command line font chooser.

@orivej
Copy link

orivej commented Jan 21, 2020

Thank you! 1.0.1 became monospace on Linux.

@philippnurullin
Copy link
Member

The v 1.0.1 is out & it fixing the bug on Win 10.

@MinchinWeb
Copy link

Thanks for getting this fixed!!

@dnelson-1901
Copy link

Looks like the https://jetbrains.com/mono webpage is still serving the 1.0.0 version when you click the "Download font" button; could someone update that too?

@philippnurullin
Copy link
Member

@dnelson-1901 Thanks for bringing this up. We will update the link after the release of 1.0.2.

@MinchinWeb
Copy link

MinchinWeb commented Jan 24, 2020

ETA on when version 1.0.2 is supposed to drop?

Five hours ago! https://github.com/JetBrains/JetBrainsMono/releases/tag/v1.0.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

9 participants