Windows doesn't recognize as mono-spaced font

[haliphax]

I had to check "allow use of variable-pitch fonts" in PuTTY to use this.

[rebornishard]

@haliphax
i used sublime with "Cosmic Sans Neue Mono"

[carlosedp]

I could not use this on gVim (Windows) as well. It does not recognizes the font.

[belluzj]

I don't know what to do, in FontForge it seems I have set to "monospaced" in every place where I could... I need advice from a Windows/FontForge guru, if anybody knows one :)

[carlosedp]

I found this post: https://groups.google.com/forum/#!topic/vim_use/PWz-m0PybSQ

Maybe it works...

[belluzj]

Ok, but the setting they talk about is already set to "monospaced", at least in the latest commit on master. Maybe you do not have the latest version?

[carlosedp]

I have the TTF ones on the repository. Are they the ones with the Powerline patch?

I had it working on Mac but gVim on Windows does not recognizes it.

[Jackbennett]

I installed this font and set it in the powershell ISE and it does indeed show up in the monospaced filter list. Renders a little rough maybe but it's there.

Tried restarting explorer.exe or the PC to see if that refreshes' some secret installed font list gVim reads?

[belluzj]

I have tried to match as closely as possible information from Consolas, and regenerated the .ttf and .otf seconds ago. Maybe taking this new version and restarting or whatever Windows magic may solve the problem?

[carlosedp]

I tried the last version from the repository. It showed as a monospaced font and worked on gVim (Windows).

There might be some problems with the rendering as you can see from the screenshot here:

Compare to Inconsolatta for powerline below:

Thanks!

[belluzj]

The biggest problems I see are big M being taller than other caps and small L having a weird top serif. Also small a and small g look a bit too fat in the middle, but I am not sure I can do something for them. Do you spot other things?

[carlosedp]

That's the issues I see. Also the 3 have a weird top and the 6 and 9 have a small pointy things over and under.

[belluzj]

Can you try the latest commit please?

[belluzj]

sorry, my push was rejected this time should be ok

[belluzj]

Windows rendering issues should be fixed by TrueType files (.ttf) from the latest version, 1.3.1. Please try them, and if it's ok, close this issue.

[carlosedp]

Rendering is perfect with last version.

[Zhichao-Hong]

The 1.6.3-beta release no longer shows the ttf fonts as monospaced on windows. Is there a fix? BTW, love this font.

[belluzj]

Can you try the latest release please? There

[Zhichao-Hong]

The latest release works fine and vim can find it. Thanks! Only one question or issue. Vim can only see the Regular and Bold style. In the Fonts control panel, the font style in Fantasque Sans Mono only display. I am sure the attached image Please see attached image.

[joqs]

Windows seems to be more picky than Linux when dealing with font names. Causing the problem that Zhichao-Hong (and me) experienced to manifest. It can be fixed by changing the TTF-sub-family-name in FontForge from "BoldItalic" to "Bold Italic" and from "RegItalic" to "Italic" and re-making. And thanks for a pleasant font!

[belluzj]

Done! Thanks for pointing out exactly what to change.