From: j.krug@lancaster.ac.uk
To: 9fans@cse.psu.edu
Subject: [9fans] Ligatures
Date: Mon, 19 Apr 2004 15:45:46 +0100 [thread overview]
Message-ID: <ab7146b9ad859a8f681a22084bc46995@lancaster.ac.uk> (raw)
Hi,
Can anyone explain how troff handles ligatures on plan9?
With this input
.TS
center allbox;
l l l l l.
\(Fi ffi ffi fb03 64259
\(fi fi fi fb01 64257
\(ff ff ff fb00 64256
\(Ae AE Æ 00c6 198
\(ae ae æ 00e6 230
\(fl fl fl fb02 64258
\(Fl ffl ffl fb04 64260
- ft ſt 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
http://en.wikipedia.org/wiki/Ligature_(typography)
Cheers,
John
next reply other threads:[~2004-04-19 14:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 14:45 j.krug [this message]
2004-04-21 22:53 ` rog
2004-04-21 23:00 ` boyd, rounin
2004-04-21 23:12 ` George Michaelson
2004-04-21 23:16 ` boyd, rounin
2004-04-21 23:41 ` George Michaelson
2004-04-21 23:58 ` boyd, rounin
2004-04-22 0:09 ` George Michaelson
2004-04-22 0:33 ` boyd, rounin
2004-04-22 0:47 ` George Michaelson
2004-04-22 1:07 ` boyd, rounin
2004-04-22 1:11 ` Geoff Collyer
2004-04-22 1:13 ` boyd, rounin
2004-04-22 1:21 ` George Michaelson
2004-04-22 1:36 ` boyd, rounin
2004-04-22 8:56 ` Dave Lukes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ab7146b9ad859a8f681a22084bc46995@lancaster.ac.uk \
--to=j.krug@lancaster.ac.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).