From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ab7146b9ad859a8f681a22084bc46995@lancaster.ac.uk>
To: 9fans@cse.psu.edu
From: j.krug@lancaster.ac.uk
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Subject: [9fans] Ligatures
Date: Mon, 19 Apr 2004 15:45:46 +0100
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 5fefc600-eacd-11e9-9e20-41e7f4b1d025

Hi,

Can anyone explain how troff handles ligatures on plan9?=20

With this input=20

.TS
center allbox;
l l l l l.
\(Fi	ffi	=EF=AC=83	fb03	64259
\(fi	fi	=EF=AC=81	fb01	64257
\(ff	ff	=EF=AC=80	fb00	64256
\(Ae	AE	=C3=86	00c6	198
\(ae	ae	=C3=A6	00e6	230
\(fl	fl	=EF=AC=82	fb02	64258
\(Fl	ffl	=EF=AC=84	fb04	64260
-	ft	=EF=AC=85	fb05	64261
.TE

piped through tbl | troff -ms | lp -d stdout generates a postscript
file that will only display the ae ligatures (whether viewed with page
or printed).

The third column is from Compose X hex-code.

Or is this a font problem (which I am still unsure how to solve)?

The last page of /sys/doc/troff.ps (the tables of special characters
include the ligatures) seems to have the same behaviour.

I got the unicode values from=20
	http://en.wikipedia.org/wiki/Ligature_(typography)=20

Cheers,
John