<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2769" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>To clear up some
misconceptions:</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>(1) EPS
(Encapsulated PostScript) is a file format developed by Adobe, not by Aldus
</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>or Altsys. It may
contain almost any combination of PostScript graphic objects
including</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>text, vector, and
raster.</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>(2) PostScript Level
2 fully supports JPEG compression. An EPS file can readily </FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>contain
JPEG-compressed images and compliant PostScript Level 2 (and PostScript
3)</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>RIPs must fully
support decoding of same. This has been part of the PostScript
standard</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>for nearly 15 years
now! Note that EPS from Photoshop can include
JPEG-compressed</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>raster images in
PostScript. Thus, if you have a RIP that cannot handle JPEG-</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>compressed images,
you really do have a very out-of-spec, defective RIP. (For
what</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>it is worth, we have
no record of any problems with Adobe PostScript-based RIPs</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>handling
JPEG-compressed images in PostScript Level 2 or PostScript
3!)</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>(3) With most layout
programs, for raster images other than those that "come in"
via</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>EPS, it is
irrelevant whether the initial format is JPEG, GIF, ZIP-compressed
TIFF,</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>LZW-compressed TIFF,
etc. The layout program typically decompresses the image</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>and then outputs the
resultant raster in a common format either through directly
or</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>driver-generated
PostScript. This is indeed true for FrameMaker!</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>(4) The primary
issue against use of GIF or JPEG formats is that of
lossiness,</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>either of detail or
of color, and of imaging artifacts. For photographic images
at</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>reasonably high
resolution, use of JPEG compression at maximum quality is</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>typically not a
problem. JPEG compression is a problem when trying to use</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>it to present text
or vector artwork as a compressed raster.</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>(5) The TrueType
issue has been discussed ad nauseum. There is no good</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>technical reason to
avoid properly created TrueType fonts from reputable
sources.</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>Within Adobe, we see
as many problems from improperly created Type 1 fonts</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>as we do from
improperly created TrueType fonts.</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>(6) Making blanket
assertions about general "unreliability" of JPEG or TrueType</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>as
</FONT></SPAN><SPAN class=624352717-06122005><FONT face=Arial size=2>formats for
raster compression and font technology respectively tends to hurt
</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial size=2>the credibility of
those who make such assertions.</FONT></SPAN></DIV>
<DIV><SPAN class=624352717-06122005><FONT face=Arial
size=2></FONT></SPAN> </DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
framers-bounces+isaacs=adobe.com@lists.frameusers.com
[mailto:framers-bounces+isaacs=adobe.com@lists.frameusers.com] <B>On Behalf Of
</B>Paul Findon<BR><B>Sent:</B> Tuesday, December 06, 2005 3:54
AM<BR><B>To:</B> Joe Malin<BR><B>Cc:</B>
framers@lists.frameusers.com<BR><B>Subject:</B> Re: FM bloat (NO
PDF)<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/plain format -->
<P><FONT size=2><FONT face="Courier New">On 5 Dec 2005, at 19:03, Joe Malin
wrote:<BR><BR>> They would be bigger than JPG.<BR>><BR>> Are you
suggesting that GIF or JPG are *not* used by publishing<BR>>
professionals?<BR><BR>No, I'm just saying that pro print publishers generally
prefer EPS and<BR>TIFF because of their heritage and foolproof output on
PostScript<BR>output devices. EPS files being nuggets of PostScript (format
developed<BR>by Adobe, Aldus, and Altsys); LZW decompression for TIFF files
(format<BR>developed by Aldus and, surprisingly, Microsoft) was wired
into<BR>PostScript Level 2 and later versions.<BR><BR>Obviously, other formats
work, too, but I don't like last-minute<BR>surprises, and try to avoid miles
of film going in the trash because a<BR>naughty file tripped up our PostScript
imagesetter. I learned the hard<BR>way 15 years ago with some home-brewed
PostScript graphics...<BR><BR>This may not be so relevant if you output to
PDF, but since Distiller<BR>is essentially a soft PostScript RIP, I always
feed it EPS and TIFF<BR>instead of lossy formats.<BR><BR>Old habits die hard,
I guess. And, no. I don't use TrueType fonts
;-)<BR><BR>Paul<BR></FONT></FONT></P></BLOCKQUOTE></BODY></HTML>