search

MonoLisaFont / feedback

Send us your feedback regarding the MonoLisa font
86 stars 2 forks source link

Ligatures don't render in MacOS terminal #41

Open bebraw opened 3 years ago

bebraw commented 3 years ago

I tested MonoLisa against MacOS default terminal. Renders below:

Fira Code

Screenshot 2020-10-17 at 12 20 11

MonoLisa

Screenshot 2020-10-17 at 12 20 51

MacOS terminal doesn't have any specific setting to enable/disable ligatures. The question is, what's causing the difference and should this be fixed?

okonet commented 3 years ago

Confirming this. Not sure how I didn't notice this before...

bebraw commented 3 years ago

Given both Fira and MonoLisa have been authored using Glyphs, I imagine it's some difference in output settings or perhaps ligature groups. Reference for comparison: https://github.com/tonsky/FiraCode .

MarcusSterz commented 3 years ago

@mekkablue Can you have a look?

bebraw commented 3 years ago

I think the difference might be due to https://github.com/tonsky/FiraCode/issues/854 . It seems FiraCode is using calt (contextual alternates) for these so we would have to move the ligatures to that group to have them enabled everywhere by default.

okonet commented 3 years ago

I'm not sure how calt and ligatures are related (afaik they are not) but since https://github.com/MonoLisaFont/website/issues/55 is still open I guess we also use calt. @MarcusSterz any comments?

okonet commented 3 years ago

Apparently Terminal only support calt so starting from v1.600 all ligatures from calt (i.e. non-symbols) will be visible in Terminal. Unfortunately we can't do much about symbols from liga and because the separation of those is a "feature" we won't act on this one anymore.

alessandrodn commented 3 years ago

Apparently Terminal only support calt so starting from v1.600 all ligatures from calt (i.e. non-symbols) will be visible in Terminal.

What's does it mean in practice? I installed version v1.600 and I don't see any difference...

okonet commented 3 years ago

It means that support for ligatures is limited it Terminal and you will only see a subset called contextual alternatives defined in calt as per https://www.monolisa.dev/specimen

repoles commented 1 year ago

So, there is still no way to enable MonoLisa ligatures in macOS default terminal, like it does when using Fire Code or JetBrains Mono?

bebraw commented 1 year ago

@repoles Did you try freezing the ligatures with the customize tool? If this does not work, please open a new issue.

repoles commented 1 year ago

@bebraw how can I freeze the ligatures? Are you mean customize the font before download? If so I didn't see any option to freeze ligatures. The only option I changed was to use script variant.

Screenshot 2023-01-19 at 12 01 57
bebraw commented 1 year ago

@repoles It's the top-right. I see it's not possible to freeze them based on that. Please open a separate issue so we don't lose the feature request.

okonet commented 1 year ago

No, it’s not possible and can’t be possible actually. I’d recommend iTerm2 which has support for ligatures.

okonet commented 1 year ago

BTW it’s only Liga that’s not working. caltworks in Terminal out of the box but there is no way to change these settings AFAIK.

repoles commented 1 year ago

I don't know nothing about how font ligature works. And I know macOS Terminal support for this feature is weak. I tried iTerm2 and other terminals, but keep preferring the basic, simple, efficient, out-of-the-box Terminal ;) But since ligatures work properly on this app when I'm using Fira Code or JetBrains Mono, I thought maybe there was a way to use the same approach to make MonoLisa work the same. But this is not a big deal, really. The font is simply beautiful and I'm happy to be able to use it with ligatures in my code editors.

okonet commented 1 year ago

Hmm, I need to check Fira Code with my Terminal.

davedice commented 1 year ago

I have the same problem on MacOS. Ligatures work as expected in iTerm2 (which I temporarily installed and removed just to test the feature), in vscode, in mvim, etc., but not in terminal.app, which is where I really wanted the feature. Other ligaturized fonts, such as Jetbrains, BerkeleyMono, Julia, Cascadia, Fira, etc., all work as expected with visible ligatures in terminal.app.

There's a comment in https://github.com/MonoLisaFont/feedback/issues/191 about augmenting customizer to allow "liga" to be merged into "calt", which would be interesting try. I took a quick look at fontforge and fontfreeze, but didn't seen any obvious way to try that myself.