Next | Query returned 5 messages, browsing 1 to 10 | previous

History of commit frequency

CVS Commit History:


   2021-10-26 12:28:41 by Nia Alarie | Files touched by this commit (864)
Log message:
fonts: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes
   2021-10-07 16:05:29 by Nia Alarie | Files touched by this commit (864)
Log message:
fonts: Remove SHA1 hashes for distfiles
   2019-11-02 23:24:44 by Roland Illig | Files touched by this commit (62)
Log message:
fonts: align variable assignments

pkglint -Wall -F --only aligned --only indent -r

No manual corrections.
   2017-05-06 03:06:43 by Makoto Fujiwara | Files touched by this commit (2)
Log message:
Updated fonts/Hasklig to 1.1
----------------------------
v1.1
   - New ligatures ->>, :::, >=>, <=<, <=>, <->
   - Switched to newer version of calt code by Nikita Prokopov. It
     "doesn’t apply ligatures to long sequences of chars, e.g. !!!!,
     >>>>, etc"
   - Fixed ++ and +++ line inconsistency in heavy italic weights
v1.0
   - Updates to the latest version of SCP
   - Hasklig moves to a ligature substitution mechanism borrowed from
    the excellent Fira Code by Nikita Prokopov
   2016-01-20 12:39:41 by Thomas Klausner | Files touched by this commit (4)
Log message:
Import Hasklig-0.9 as fonts/Hasklig.

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, 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.

Next | Query returned 5 messages, browsing 1 to 10 | previous