Hasklig - a code font with monospaced ligatures

I think the title says it all - I worked on a PR which recently got merged into mainline MacVim which enables ligature support for the CoreText renderer :smile_cat:

• https://github.com/adobe-fonts/source-code-pro/issues/250
• https://github.com/microsoft/vscode/issues/100840
• https://bugs.chromium.org/p/chromium/issues/detail?id=1100502

As per the title. Do I need to take extra steps to get Hasklig working in VS Code?

VS Code not picking up Hasklig's ligatures. But the font is changed to Source Code Pro. And also showing KDE's font config utility picking up Hasklig's ligatures without any issues.

On the exact same box, simultaneously, KDE's KDevelop is picking up Hasklig's ligatures without any issues.

Edit: And KWrite and Kate (also on the exact same box) picking up Hasklig's ligature's correctly.

This would enable cursor positioning "inside" ligatures in atom (see this and this). Would also help with #18.

I really love hasklig but the unintuitive insertion point behavior around the combination glyphs sends me back to plain Source Code Pro. :cry:

Thanks for making Hasklig! :heart:

I tried setting up this font in Atom, and after I disabled hardware acceleration and added body { text-rendering: optimizeLegibility; to my css configuration, it seemed to work, but the cursor shows up in the wrong place (and it gets worse the more ligatures you have in a line). The cursor shown here is actually at the end of the line:

I just want to clarify if Atom has been able to use the font with full support before in a different config/version/system. I'm using the current version 0.146.0 on Ubuntu 14.04.

I try to build the font using Ubuntu on WSL, but I encounter the problem in the title.

What I've done

I have installed afdko and fonttools using pip3 install afdko fonttools and ran the ./buildInstances.sh command which resulted in:

[email protected]:/mnt/c/Users/cdrozak/Projects/Hasklig$ ./buildInstances.sh
./buildInstances.sh: line 1: makeInstancesUFO: command not found
./buildInstances.sh: line 2: makeInstancesUFO: command not found

When I changed makeInstancesUFO to lowercase, I got the following response:

[email protected]:/mnt/c/Users/cdrozak/Projects/Hasklig$ ./buildInstances.sh
ERROR:afdko.makeinstancesufo:No axes defined
ERROR:afdko.makeinstancesufo:No axes defined

Created with https://github.com/dkhamsing/frankenstein

GitHub Corrected URLs

| Was | Now | | --- | --- | | https://github.com/Lokaltog/powerline | https://github.com/powerline/powerline | | https://github.com/adobe/source-code-pro | https://github.com/adobe-fonts/source-code-pro |

HTTPS Corrected URLs

| Was | Now | | --- | --- | | http://en.wikipedia.org/wiki/Typographic_ligature | https://en.wikipedia.org/wiki/Typographic_ligature | | http://www.andres-loeh.de/lhs2tex/ | https://www.andres-loeh.de/lhs2tex/ |

While Hasklig ligatures work, if you toggle text-rendering: optimizeLegibility (needed for ligatures) on NW.js 0.12.x, which is using embedded Chromium 41.0.2272.76, the line-length of the "monospaced" font changes. text-rendering: geometricPrecision has the same error.

See: https://github.com/Crunch/Crunch-2/issues/39

This is probably why support has been difficult for Chromium-based editors like Atom. The Hasklig font simply doesn't render as a monospace font.

Just that, really. :smile:

I really like Hasklig, but for some reason I can't stomach the dotted zero, so I was wondering if you'd consider adding a version with it slashed, kind of like what Meslo LG does.

Thanks.

Ideally should only happen after a comma, open parenthesis or space, or never after an alphanumerical character:

foo(); foo(∅); foo(bar, ∅); ∅

Other rust ligatures could be

&[ r#" foobar "

Intellij Idea now supports ligatures http://blog.jetbrains.com/idea/2016/06/intellij-idea-2016-2-eap-case-only-renames-in-git-ligatures-background-images-and-more/

The script with is called on makeInstances.sh is makeInstancesUFO. But the name of the script is makeinstacesufo, so it must either be changed to makeInstancesUFO or makeintancesufo in makeInstances.sh.

I'm using vscode with Hasklig as the font. But for languages other then Haskell I have disabled ligatures.

When using Haskell I have no problems. But when using non-Haskell it works fine for the most part but any l l in the text is rendered as a weird double l symbol. See the gif.

https://user-images.githubusercontent.com/7439756/152345946-fc1c9993-5db0-4f17-9d97-46611fa7c631.mp4

I'm unsure what the issue is. Or whether it's Hasklig or vscode or even some weird config on my end.

Hi everyone!

I like this font so much that I'm using also as the desktop interface font for my Linux systems, not just as the font for the coding parts.

Now, I'd like to use it for my web presentations (ok, locally still doable with otf/ttf) and web blog. As I couldn't find any woff and/or woff2 version of it, nor another reference about it in the issues, I am asking here: any reason not to OR plan to release the webfonts version of it :grey_question:

Thanks.

This PR addresses a couple of small build issues I had while attempting to build Hasklig (environment dump below). These changes shouldn't affect the current build process but should expand build support to Linux systems.

1. Build scripts are now executed under the BASH runtime rather than SH.

2. makeInstances.sh supports the case-sensitive version of 'makeinstancesufo'.

Environment Dump:

  Operating System: Ubuntu 21.04
            Kernel: Linux 5.11.0-38-generic
      Architecture: x86-64

Thanks in advance. Forgive me if I've missed something silly.

I just downloaded a zip of the 1.2 release and tried to use it with Kitty terminal, which only uses monospace fonts. Long-story-short, it seems that the italic face is failing fontconfig's test for monospace font:

> fc-list : family spacing outline scalable | grep -i "hasklig"Hasklig:spacing=100:outline=True:scalable=True
Hasklig:outline=True:scalable=True
Hasklig,Hasklig Black:spacing=100:outline=True:scalable=True
Hasklig,Hasklig Semibold:spacing=100:outline=True:scalable=True
Hasklig,Hasklig Light:outline=True:scalable=True
Hasklig,Hasklig Semibold:outline=True:scalable=True
Hasklig,Hasklig Light:spacing=100:outline=True:scalable=True
Hasklig,Hasklig Medium:outline=True:scalable=True
Hasklig,Hasklig Medium:spacing=100:outline=True:scalable=True
Hasklig,Hasklig ExtraLight:spacing=100:outline=True:scalable=True

Or likewise:

> fc-list :mono family | grep -i "hasklig"
Hasklig
Hasklig,Hasklig Black
Hasklig,Hasklig Light
Hasklig,Hasklig Semibold
Hasklig,Hasklig Medium
Hasklig,Hasklig ExtraLight

I don't know anything about fonts, but it looks like fc uses some property called 'advances' to rule a font FC_MONO? So if the advances of each glyph are all "approximately equal" then the font is monospace: https://github.com/behdad/fontconfig/blob/5b41ded2b0ddb98a07ac86264b94403cb7a0fd82/src/fcfreetype.c#L2348

I'm not even sure this is a bug, but let me know if I can help.