Attached is a PDF, 5981-9354EN.pdf, which seems to be a otherwise normal PDF. 
When converted to postscript, this file explodes to almost a gigabyte.  However,
when I remove -dUseCIEColor from the commandline, a normal 33MB PS file results.

The command I ran to create the file is:

/c/gs/gs8.14/bin/gswin32c -sDEVICE=pswrite -sOutputFile=out.ps -dNOPAUSE -dBATCH
-dSAFER -dUseCIEColor -dAutoRotatePages=/None' 5981-9354EN.pdf

I've looked at the PDF and the resulting PS and the problem seems to be related
to colorspaces (particularly when removing -dUseCIEColor fixes the problem,
albeit with skewed colorspaces).  About 80% of the postscript is giant blocks of
code that looks like:

	12 19 13 rG
	398 7737 2 3 rf

I poked around the PS header and I think this basically says "set the color,
then write some pixels".  If the high-level CIE colorspace in the PDF could not
be encoded in postscript, I would expect something like this.  But a 100-fold
increase in file size?

I realize the postscript device has no high-level colorspace handling yet...is
that the source of this problem?  Is there some other way to avoid making such
expensive redundancies?