From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <fd10b999e50a289fcfc7e21e3c892080@gmx.de>
Date: Sun, 18 Sep 2011 07:55:27 +0200
From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: [9fans] toff fonts
Topicbox-Message-UUID: 2793c4e6-ead7-11e9-9d60-3106f5b1d025

trying to render special unicode character 0x2019
in troff.

but pr2post fails with:

/386/bin/aux/tr2post: <stdin>:31 :WARNING: cannot find glyph, rune=0x2019 stoken=<’> troff font R

now looking in:

/sys/lib/postscript/troff/R

0x2000 0x20ff LucidaSansUnicode20

but in:

/sys/lib/troff/font/devutf/R

there is no reference to 0x2019 at all, only in

/sys/lib/troff/font/devutf/LucidaSans:12: ' 32 2 8217 2019

setting to front to LucidaSans in the troff source works.

so whats the relation between /sys/lib/postscript/troff/*
and /sys/lib/troff/font/dev*/*?

should the stuff in /sys/lib/troff/font/dev*/* be autogeneated
somehow?

--
cinap