🚀 go-pugleaf

In article <26760@life.ai.mit.edu> bkph@wheat-chex.ai.mit.edu (Berthold K.P. Horn) writes:
>
>Finally:  Let's hope that UNICODE with its 16-bit characters will help
>resolve some of these problems.  Although, UNICODE is dead in the
>water if it does not provide access to ligatures.  For there can be
>no fine typesetting without ligatures.

As I've said before, Unicode and ligatures are completely orthogonal issues.
I have on my machine right now a Unicode font containing almost 1,000 glyphs,
including scores of ligatures. The ligatures, like the rest of the
typographic richness of this font, are accessed via a well-defined method
that has *nothing* to do with the character encoding (i.e. Unicode).

Unicode encodes meaning. Ligatures are inappropriate in this context.

Fonts encode appearance. Ligatures, swashes and everything else are very
appropriate in this context.

Dave Opstad
Line Layout Weenie