Remove slash_equal ligature
“/=” is a valid operator in C but it does not mean unequal, so it should not be rendered as such.
|4 weeks ago|
|Italic||2 years ago|
|ItalicMasters||4 weeks ago|
|Roman||2 years ago|
|RomanMasters||4 weeks ago|
|emoji||3 years ago|
|svg||2 years ago|
|.gitignore||1 year ago|
|FontMenuNameDB||4 weeks ago|
|GlyphOrderAndAliasDB||4 weeks ago|
|README.md||1 year ago|
|SourceCodeProSample.png||3 years ago|
|addSVGtable.py||4 weeks ago|
|all.rtf||4 weeks ago|
|build.cmd||4 weeks ago|
|build.sh||4 weeks ago|
|buildInstances.sh||4 weeks ago|
|family.fea||2 years ago|
|gen_calt.clj||2 years ago|
|hasklig_example.png||4 years ago|
|ligatures.fea||4 weeks ago|
|tables.fea||3 years ago|
|uvs.txt||1 year ago|
|widthsAdjust.fea||2 years ago|
|widthsAdjust.mark||6 years ago|
N.B. This is a fork of the Source Code Pro repository
Programming languages are limited to relatively few characters. As a result, combined character operators surfaced quite early, such as the widely used arrow (
->), comprised of a hyphen and greater sign. It looks like an arrow if you know the analogy and squint a bit.
Composite glyphs are problematic in languages such as Haskell which utilize these complicated operators (
>>= etc.) extensively. The readability of such complex code improves with pretty printing. Academic articles featuring Haskell code often use lhs2tex to achieve an appealing rendering, but it is of no use when programming.
Some Haskellers have resorted to Unicode symbols (
← etc.), which are valid in the ghc. However they are one-character-wide and therefore eye-strainingly small. Furthermore, when displayed as substitutes to the underlying multi-character representation, as vim2hs does, the characters go out of alignment.
Hasklig solves the problem the way typographers have always solved ill-fitting characters which co-occur often: ligatures. The underlying code stays the same — only the representation changes.
Not only can multi-character glyphs be rendered more vividly, other problematic things in monospaced fonts, such as spacing can be corrected.
+++line inconsistency in heavy italic weights
==>, Powerline symbol support
/=to match other equals signs
This list is compiled based on reports on the current state of support for code editors and terminals. This list
To build the binary font files from source, you need to have installed the Adobe Font Development Kit for OpenType (AFDKO). The AFDKO tools are widely used for font development today, and are part of most font editor applications.
Some SVG glyphs are inserted into the fonts using Python FontTools.
This repository only includes so-called master weights of the fonts (effectively extralight and black).
The shapes of the weights in between these extremities are calculated by
makeInstancesUFO supplied with
For convenience, the shell script buildInstances is provided, which executes
makeInstancesUFO, calculating all the italic and regular font weight shapes.
The key to building OTF or TTF fonts is
makeotf, which is part of the AFDKO toolset.
Information and usage instructions can be found by executing
In this repository, all necessary files are in place for building the OTF and TTF fonts. For example, build a binary OTF font for the Regular style like this:
$ cd Roman/Regular/ $ makeotf -r
For convenience, a shell script named build is provided in the root directory. It builds all OTFs and TTFs, and can be executed by typing:
or this on Windows:
Original idea, design and implementation of code ligatures by Ian Tuomi 2014-2015. This typeface extends Source Code Pro with ligatures.