ignatov / haack

Hæck

Hæck

Hæck is the Hack fork with programming ligatures.

Download v0.1.

Code examples

Java

Kotlin

Go

Erlang

Ruby

haack's Issues

ligatures aren't used in IntelliJ

When I use Fira Code, they are used so not sure if this is a problem with the font or the tool? Also, it doesn't register as a monospaced font - maybe that's why?

>>> ligature?

Useful for Python (Prompt) and also Scala (which I do not use)

Add && ligature

Upstream Build and Hinting Process in Hack

Copied from the thread: source-foundry/Hack#35 (comment)

For ttf files (recommended for use across all platforms), I built with FontLab V as “pre-hinted” ttf build files, then used our ttfautohint based scripted hinting approach that is contained in the following script file:

https://github.com/chrissimpkins/Hack/blob/master/postbuild_processing/tt-hinting/autohint.sh

This uses hinting settings that are defined in the -TA- files in this directory:

https://github.com/chrissimpkins/Hack/tree/master/postbuild_processing/tt-hinting

These files apply optimized hinting to the main character set files that are used in code. We never ran through optimizations for extended character sets that were not commonly used in code because this was not our goal. If you replicate this approach, you will get hinting in your new ligature characters (ttfautohint hints all characters in the set) but you may need to tweak these if you find that they do not look as intended at certain glyph sizes.

For otf files, the build files are hinted with the built in otf hinting used in FontLab V. You will get good automated hinting of otf files in Glyphs as well (probably better c/w FontLab).

On OS X, the hinting is automated by the operating system and hints are ignored. TTF and OTF files should both look similar and good.

For Windows and Linux, the hints really, really matter (see a large number of the closed issue reports) and I suggest that you investigate how your new glyphs appear at a range of sizes commonly used in code editors if you are targeting these platforms.

Anyone can repeat this process on Haack ttf build files. Feel free to grab all hinting files and implement in a Haack specific manner in this fork.

Information about ttfautohint: https://www.freetype.org/ttfautohint/

Information about Control Instructions Files to optimize the automated hinting with ttfautohint in all new glyphs that you add and other glyphs that were not further optimized upstream: https://www.freetype.org/ttfautohint/doc/ttfautohint.html#control-instructions

Best of luck guys! Look forward to seeing what you create. And if you put ttfautohint to good use, pitch some beer money in @lemzwerg 's jar to keep the lights on. He provided us with a tremendous amount of help with the ttf hinting in Hack and we are big fans of ttfautohint.

Change font family name

Typing Hæck is going to be difficult (at best) for many users. Haeck or Haack would work (and the latter was what I expected from the repo name).

Add === and !== ligatures

Would be great for JavaScript.