From 84f24f428928a83276fec3a8974ad4578926baf0 Mon Sep 17 00:00:00 2001 From: Ian Tuomi Date: Sun, 20 Apr 2014 04:31:33 +0300 Subject: [PATCH] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d12e7c0030..a0e1e4399c 100644 --- a/README.md +++ b/README.md @@ -1,15 +1,15 @@ _N.B. This is a fork of the_ [Source Code Pro repository](https://github.com/adobe/source-code-pro) -##Code Ligatures +## Code Ligatures Programming languages are limited to relatively few characters. As a result of a limited character set, 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 become especially problematic in languages such as Haskell which utilize these complicated operators (`<-`, `::`, `=>`, `-<`, `>>=` etc.) extensively (over 100 in `lens` alone!). Prettified code improves readability considerably - some Haskell programmers have even resorted to unicode symbols (ie. `⇒`, `←` etc.). This merely opens a whole new can of worms. In addition to encoding/compatibility problems and all the reasons it never worked out in APL, these symbols are one-character-wide and therefore eye-strainingly small. -Source Code Pro L solves this 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. +Hasklig solves this 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. #### Hasklig -![Source Code Pro L Sample](SourceCodeProLSample.png?raw=true) +![Hasklig Sample](SourceCodeProLSample.png?raw=true) #### Source Code Pro ![Source Code Pro Sample](SourceCodeProSample.png?raw=true)