Xref: utzoo comp.lang.postscript:8519 comp.fonts:2429
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!hellgate.utah.edu!dog.ee.lbl.gov!nosc!humu!pegasus!richard
From: richard@pegasus.com (Richard Foulk)
Newsgroups: comp.lang.postscript,comp.fonts
Subject: Re: EPS Recycle Logos
Message-ID: <1991May2.134830.18159@pegasus.com>
Date: 2 May 91 13:48:30 GMT
References: <1991Apr20.143129.23254@watdragon.waterloo.edu> <1991Apr24.005215.17466@ico.isc.com> <1991Apr25.040156.2883@pegasus.com>
Organization: Pegasus,  Honolulu
Lines: 65

In article <1991Apr25.040156.2883@pegasus.com> richard@pegasus.com (Richard Foulk) writes:
>>> The following two uuencoded files are EPS (encapsulated postscript)
>>> versions (including 300 dpi TIFF bitmaps for display by PageMaker, etc.)
>>> of recycle logos I have drawn.
>>
>>As received here, after uudecoding, they each had 30 bytes of garbage ahead
>>of the %!.  What I presume to be the bitmaps were glued on right after the
>>"showpage" line.  Good for choking a spooler; otherwise requires editing.
>
>As hideous as it seems that's a valid EPS (of the tiff kind).
>
>It should really be called a tiff file with a postscript comment.

My apologies.  It looked like a valid EPS file, the header has the
necessary magic cookie, but the tiff doesn't work with anything I've
got either.

Note though, that the Adobe document; "Encapsulated PostScript File Format"
does specify an EPS file format that contains a binary header and embedded
binary in the form of a TIFF image.

Here's a quote from that document for your edification (horrification?).

(Don't read this just before lunch.)

---------------------begin quote--------------------------------

MS-DOS: MetaFile or TIFF Representation

Either a Microsoft Windows MetaFile or a TIFF (Tag Image File Format)
section can be included as the screen representation of an EPS file.
The file format for EPS files is:

Header:		Bytes		Description
		0-3		Must be hex C5D0D3C6 (byte 0=C5)
		4-7		Byte position in file for start of
				PostScript code section.
		8-11		Byte length of PostScript section
		12-15		Byte position in file for start of Metafile
				screen representation.
		16-19		Byte length of Metafile section (PSize)
		20-23		Byte position of TIFF representation
		24-27		Byte length of TIFF section
		28-29		Checksum of header (XOR of bytes 0-27)
				NOTE:  if FFFF then it is to be ignored.

Body:		Bytes		Description
		0-PSize-1	Metafile contents (according to Microsoft
				specification for Windows)

Note:  It is assumed that either the MetaFile or the TIFF position and
length fields are zero; only one or the other of these two forms are
included in the EPS file.
---------------------end quote--------------------------------

I get the impression that somebody like Microsoft whipped up this format
and then Adobe was pressured to accept it as an EPS.

So, yes, there is "valid" EPS code that you can't send to your printer.




-- 
Richard Foulk		richard@pegasus.com