[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Behaviour of \latinfamily
- To: Sebastian Rahtz <s.rahtz@elsevier.co.uk>
- Subject: Re: Behaviour of \latinfamily
- From: Rebecca and Rowland <rebecca@astrid.u-net.com>
- Date: Sat, 30 May 1998 03:30:46 +0100
- Cc: fontinst@cogs.susx.ac.uk
- In-Reply-To: <5789-Fri29May1998103406+0100-s.rahtz@elsevier.co.uk>
- References: <l03130306b193edc0fb27@[194.119.133.41]><l03130306b19248922e17@[194.119.133.49]><199805261412.QAA19115@attila.uni-duesseldorf.de><5799-Thu28May1998095608+0100-s.rahtz@elsevier.co.uk><l03130306b193edc0fb27@[194.119.133.41]>
>Rebecca and Rowland writes:
> > Right (I think). So fontinst begins by writing xxx8r.mtx which it also
> > turns into xxx8r.pl? And you rely on the dvi driver/printer to encode the
> > `real' Type 1 fount in 8r encoding?
>no, i rely on the instructions i give eg dvips in its map file. its not
>built into dvips
The re-encoding *is* built into dvips. OzTeX's QuickDraw dvi driver can't
re-encode; dvips can. You rely on dvips to do the re-encoding. Of course
it needs the instructions to do it, but it does do it. The other way of
doing it would be to use the vf mechanism to re-map 8r->8a (or whatever),
but that means you miss out glyphs that are un-numbered in the native
encoding.
I think we've been talking at cross-purposes here.
Rowland.