[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: huh?
- To: alanje@cogs.susx.ac.uk (Alan Jeffrey)
- Subject: Re: huh?
- From: Petr Sojka <sojka@daeron.ics.muni.cz>
- Date: Mon, 16 May 1994 19:03:14 +0200 (MET DST)
- Cc: ls@mathp7.jussieu.fr, andrew.trevorrow@anu.edu.au, barry@bluesky.com, math-font-discuss@cogs.susx.ac.uk, rokicki@cs.stanford.edu, zlatuska@muni.cz (Jiri Zlatuska)
- Content-Length: 575
- Organization: Masaryk University, Brno, The Czech Republic
- Postal-Address: Institute of Computer Science, Buresova 20, 60200 Brno
- Telephone: +42-5-41321237 ext. 283, Fax: +42-5-41212747
Alan dixit:
: Perhaps the best solution is to have the dvi driver save the current
: value of drift when it hits a VF (PUSH), then zero the drift inside
: the (PUSH)...(POP), and restore the value of drift at the (POP). So
: unless the virtual characters are particularly complex, the maxdrift
: algorithm won't affect the placement of the components of the
: composite character.
This will result in resolution dependent .dvi files (what should
dvicopy do knowing nothing about resolution of the output device?)!
Or should dvicopy be `disabled' then?
Petr <sojka@muni.cz>
- Follow-Ups:
- Re: huh?
- From: alanje@cogs.susx.ac.uk (Alan Jeffrey)
- References:
- Re: huh?
- From: alanje@cogs.susx.ac.uk (Alan Jeffrey)