No ligatures version

[f2l2pe]

It would be nice to have a version without ligatures because some softwares can't disable them like Visual Studio 2019, and some people ( like me ) don't like them.

Thank you!

[cipriancraciun]

@philippnurullin I'm not acquainted with font creation or worflow, but the way I see it, the following are a few advantages of providing the same set of fonts (normal and NL) in all formats:

• first of all it keeps people from forking the project, or worse proliferating a "version" or "variant" hell; (for example there are already 57 forks, granted out of which only ~10 are active; and most of these are already one or two versions behind;)

• secondly it provides users with an "out-of-the-box" experience; (i.e. you have the NL variant in TTF, you can find it also for the web;)

• now regarding strictly web-fonts, when this font initially appeared, I've installed it and configured it as my default font in Firefox and Chromium, and although I've not enabled ligatures anywhere (I'm assuming they are on by default?) and moreover I've explicitly disabled font ligatures via userContent.css as font-variant-ligatures : none !important;, they still applied;

• regarding the "weight" of the download, yes 80KiB does matter especially since it's 80KiB per font file, and you need at least regular, italic and bold, thus ~250KiB, and given that the usual whole page + CSS is less than half that, I would say it matters;

• regarding the "do it on your own", I would say that once this font is uploaded on a CDN (like for example https://cdnjs.com/), it would be nice to have these options also;

Anyway, given that (I assume) there is an easy CLI converter from TTF to web-format, I think it would be a shame not including it in the make (or choosen build system) to automatically generate it.

[Cirzen]

Hi, I have no idea how the files are getting in to brew. Sorry. @philippnurullin : On a similar note, the Chocolatey package has been setting the download location as the Jetbrains site rather than Github, but 1.0.4 isn't up there yet. Will this version be ending up there too, or should I move the default download location to Github?

[f2l2pe]

Thanks for accepting the suggestion! Now we just need a slashed zero variant and Jetbrains Mono SLSZ will be my favorite font :P

[philippnurullin]

@cipriancraciun

• I believe if you setting some font as a default in your browser it will be taken from OS, so the web format won't help in your use case.
• The current statistics on web page size is something around 1,7—2MB, including images. https://httparchive.org/reports/state-of-the-web?start=2018_12_15&end=latest&view=list Just to be precise the difference in size of Liga fonts you mentioned to be "default package" (Regular, Italic, Bold) vs No Liga is 177KB. So, the impact is not so big.

Regarding all the argument on this matter, we will be happy to make the NL full format package but there is a huge problem of overcomplicating the repository. When the 3—4 lighter weights will be introduced there will be a lot of files. The one solution is to make separate folders with the same structure for NL & L versions, but i think we can do better. For now the NL version will only be provided in .ttf format. Sorry if i disappoint you.

@Cirzen It will be more convenient to take files from GitHub. The updated versions coming to the site a bit late. Thanks!

@chiniara The slashed zero can be turned on by zero OpenType feature. You can read about it in here https://github.com/JetBrains/JetBrainsMono/issues/8

[cipriancraciun]

[This is the last time I advocate for inclusion of NL in other formats.]

The current statistics on web page size is something around 1,7—2MB, including images. https://httparchive.org/reports/state-of-the-web?start=2018_12_15&end=latest&view=list Just to be precise the difference in size of Liga fonts you mentioned to be "default package" (Regular, Italic, Bold) vs No Liga is 177KB. So, the impact is not so big.

@philippnurullin even so, at ~1.7 MiB per page, a ~170 KiB reduction is 10%...

Moreover if everyone takes the same approach: "at the moment metric M is {base}, thus an increase of {+delta}% is not an issue" we'll soon end-up with ~10 MiB per web page... (We got here just through this kind of incremental justifications...)

[philippnurullin]

@cipriancraciun Ok, legit point. To keep things related & clean, i will close this issue because the general request was to add No Ligature version.

I you have more suggestions or stumble upon a problem, please create a new issue.

[ghost]

Is there a variable font of this? Basically ./variable/JetBrainsMonoNL[wght].ttf and ./variable/JetBrainsMonoNL-Italic[wght].ttf

[philippnurullin]

@SNDST00M No. If you IDE support variable fonts it is 100% supports OpenType features, so you can turn off ligatures and use default version.

[ghost]

As we've established that NL is necessary for IDEs like Eclipse, is this reason enough to generate & ship a variable NL font?

[philippnurullin]

@SNDST00M Can't find anything about support of variable font in Eclipse. Are they working in it?

[ghost]

I can select variant ("font style") in appearance, it works okay.

Ideally I would want to install all no-ligature variants in one font file though 🤔

[philippnurullin]

On the screenshot there is a non variable version of JetBrains mono. Please install the variable font JetBrainsMono[wght] to test support of variable fonts in Eclipse.

[ghost]

Already installed a while back

[philippnurullin]

Ok, nice. Thanks for the feedback. We will think on adding the NL variable.

[jyxjjj]

What is the situation currently? Of NL Variable

[myfonj]

Sidenote: Wiki now contains guidance for disabling either complete support of "ligatures" (Contextual alternates) through OpenType settings ("calt" off) or just making 'sane' double/triple equals with gaps through a stylistic set ("ss19" on), see https://github.com/JetBrains/JetBrainsMono/wiki/OpenType-features .