Thierry Bouche Thierry.Bouche@ujf-grenoble.fr
Fri, 15 Jan 1999 14:00:46 +0100 (MET)


I remembered that some integer constant in fontinst allowed to produce
a letterspaced (track-kerning) font at once. I can't find it
anymore. Has this vanished (optimization against all those 0 width
RULEs? also known as semi-infinite negative width rules;-) or did I

Anyway, does someone have a simple solution to this problem: do i have
to \resetglyph _all_ encoded glyphs  la \cscglyph? or can i hook the
kerning code somewhere?

Thierry Bouche, Grenoble.

From r.m.b.lindgren@usit.uio.no 17 Jan 1999 16:09:20 +0100
From: Rolf Marvin B|e Lindgren <r.m.b.lindgren@usit.uio.no>
Date: 17 Jan 1999 16:09:20 +0100
To: fontinst@cogs.susx.ac.uk
Subject: (dvi)PS encoding
Message-ID: <12351.918486269.19@NO-ID-FOUND.mhonarc.com>
MIME-Version: 1.0
Content-Type: text/plain

having finally come to grips with how fontinst does its stuff, I'm
planning to set up a batch job to set up an obscene amount of PS fonts
to the new encoding scheme.

the remaining problem is to create the new psfonts.map file.  once a
long time ago I asked if fontinst could be made to write out a suitable
psfonts.map entry as it went along, but that would tie it too closely to
dvips, I was informed.  and I'm sure there still are people around who
use dvitps, dvi2ps, or even dvihplj (actually, that's what most people
including the Germans do, they say).  

anyway, so I thought I'd write a program to do it.  but has anybody
already done this?  written _something_ to automate the generation of
psfonts.map entries?  

Rolf Lindgren