Can't choose this font anymore in PyCharm on Linux

[manuelbua]

Don't know if that's related to the renaming or the PyCharm IDE, but the latest Cosmic Sans was working flawlessly, i could choose "CosmicSansNeueMono" just fine: i then updated to the latest version via AUR (Arch Linux) and now i can't even look it up in the font selection. Any ideas?

EDIT: just to add this is one of the most awesome coding fonts i've seen in a lot of time, this is even better than Monaco, Menlo and Meslo! Keep up the fantastic work!

[belluzj]

Could you try again with the latest version please? I did not change much, just added spaces to the family name (because it looks better, not because of this issue). As for me, the font works in all my applications, although I did not have PyCharm installed to try with it.

[manuelbua]

Just tried, but still the font can't be choosen: all other applications work fine for me too, only PyCharm won't see it: when i've more time i would like to checkout an older revision and try that, hopefully i can pinpoint what's the "problem" although it doesn't look like a font problem really. I also tried to update my ttfhinter but that's not the problem either.. will update if something change btw, thanks for getting back to me.

[manuelbua]

Ok, some more trying: i did some testing and all build up to 06adb7eef (inclusive) are working fine, is it possible that the "automate font generation" commit immediately following it (757342a72) is missing some steps or doing things differently from when you manually generated them? Could you please tell me how did you generate the fonts in the past? I tried to add an 'opentype' flag to the Python script in validate-generate.sh but nothing really changed.

[manuelbua]

Another thing i noticed is: as soon as i open any monospaced font source, i.e. FantasqueSansMono-Regular.sfd, then opening Element->Font Info, looking at "PS Names", then switching focus with the mouse beetween "Fontname" and "Name for Humans" will trigger an automatic rename for the "Name for Humans" field, removing the "Regular" part, hinting that something isn't good with minuses? I'm gonna try to remove them..

[belluzj]

Thanks for your work! Try also with the "dummy-dsig" flag, like in the following code. I remember checking this box in FontForge when I still used the GUI.

font.generate("${basename}.ttf", flags=("opentype", "dummy-dsig"));

[belluzj]

The thing about the minus sign disappearing does not happen on my computer, to me it looks more like a FontForge bug. This dash was somehow suggested by someone else, who certainly knows better than me why it should be here. I would not touch it.

[manuelbua]

Tried that too, the only way i can select the font again is to manually export it from sources, but for some reason only a very odd italic is being used with this font, looks like automatic italic :) Oh well, need to also try with/without ttfautohinter.. :shit:

[manuelbua]

Some updates: here is a simple Java snippet i wrote to leave it running with watch -n1 "java ListJavaFonts |grep -i fantasq" so that i can see when java sees the font while trying. At this time, still no luck: i can "see" the font successfully if exported by-hand from fontforge and i rename it without the minus symbol and rename the fields in fontforge too, but for some reason the font named "MonoRegular" appear as italic and no way to change that.

[belluzj]

When I run your script on my machine, using script-generated fonts, the output is:

Fantasque Sans Mono
FantasqueSans

It looks good to me... Plus I can choose the font in Eclipse, which uses Java. Please note that when I install the fonts I always run fc-cache -f after.

[manuelbua]

I can choose the font in Java too, but the snippet will not output the font on my machines: i don't know what's up then.. i may update this issue in the future with more information in case, but feel free to close it, PyCharm has always been a bit "odd" with font selection for me..

[belluzj]

I think it's on your side then. I will reopen if other people are concerned.