<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 5.00.2919.6307" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=810030805-09062001>And
again, as I mentioned in an earlier message, watch out for the fonts
that</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=810030805-09062001>distiller does not embed by default. This issue
can really come back to haunt</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=810030805-09062001>you,
as not everyone has all of the fonts you may be using loaded on their
machine...</SPAN></FONT></DIV>
<BLOCKQUOTE>
<DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Y&Y Support
[mailto:support@YandY.com]<BR><B>Sent:</B> Friday, June 08, 2001 4:39
PM<BR><B>To:</B> Prof Brian D Ripley; Ross Moore<BR><B>Cc:</B>
pdftex@tug.org<BR><B>Subject:</B> [pdftex] Re: Ghostscript vs. Acrobat Reader
quirks<BR><BR></DIV></FONT><FONT size=3>At 07:36 1999-11-23 +0000, Prof Brian
D Ripley wrote:<BR><BR>
<BLOCKQUOTE class=cite cite type="cite">> > One work around is to tell
DVIPS *not* to embedd the fonts, and then tell<BR>> > Distiller via a
menu item where to go look for the font files itself...<BR><BR>Um.
PC-centric again (from Y&Y?). Unix versions of Distiller do
this<BR>via environmental variables and seem to have much more control (they
can<BR>use resource databases).</BLOCKQUOTE><BR>Well, normally Distiller finds
the fonts itself. But it does provide the<BR>option to control which of the
directories it finds with fonts are to <BR>actually be used. Handy when
you have different versions or some<BR>junk fonts.</FONT>
</BLOCKQUOTE></BODY></HTML>