[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 8r encoding + xdvi :-(
- To: kb@cs.umb.edu, te@informatik.uni-hannover.de, vojta@math.berkeley.edu
- Subject: Re: 8r encoding + xdvi :-(
- From: vojta@math.berkeley.edu (Paul Vojta)
- Date: Tue, 30 May 1995 13:11:51 -0700
- Cc: da@dcs.ed.ac.uk, joachim.schnitter@sap-ag.de, s.rahtz@elsevier.co.uk, tex-fonts@math.utah.edu
On Tue May 30, Thomas Esser <te@informatik.uni-hannover.de> writes:
> Using c) [pbkl.gsf+gsftopk+xdvi] some positions in the fonttable are missing
> or broken:
> - the ligatures for fi and fl are just a small dot
> - empty positions: 204, 205, 206, 214, 226, 227 and more ...
> - the accents are not correctly placed over the characters, e.g.
> position 300
>From what I can tell, the only problem with pbkl.gsf+gsftopk+xdvi that does not
also occur with pbkl.gsf+dvips+gs is that certain characters are reduced to
small dots (or empty). This does not occur in gs 2.6.1 (more precisely,
with gsfonts-2.6.1); the difference seems to be that the definition, e.g.,
of /endash changed from
/endash 21 -! 10bf317005b6d52e1aa2bdbf46ffb661693922e818 |-
to
/endash{(--) Private/compose get exec} |-
In this case Private/compose seems to interfere with charpath + pathbbox
used in gsftopk. I'll try to come up with a workaround soon.
--Paul Vojta, vojta@math.berkeley.edu