scott@talarian.UUCP (Scott Weitzenkamp) (01/22/91)
My company is in the process of evaluating color PostScript printers, and I am trying to find utilities that can convert X window dump format (xwd) into color Encapsulated PostScript (EPSF) files. I read the FAQ from comp.windows.x, and downloaded xwd2ps from uunet (mod date on xwd2ps.tar.Z was 10-10-90, BTW). This is on a SPARCstation 1 with SunOS 4.0.3c and MIT X11R4 (patches 1-9). Our goal is to import these screendumps into FrameMaker 2.1X. I know that Frame can import xwd files directly, and we are also trying that approach. I want EPSF format so that we can import them into other packages that do not understand xwd format. I can use "xwd" to get my window dumps OK. I can also use "xpr -device ps" to convert to a PostScript file that prints on an Apple LaserWriter Plus just fine. I tried using xwd2ps to produce a EPSF file. I imported the EPSF file into Frame 2.1X, saved it, and printed it. The problem is that these files take forever to print (and sometimes don't seem to print at all!). Why are the EPSF files xwd2ps produces so slow? I also tried previewing the two files (produced by xpr and xwd2ps) with dxpsview on a DECstation with Ultrix 3.0. I was able to preview both files, but it took dxpsview 100 seconds to load the EPSF file vs. 2 seconds to load the normal PostScript file. This is really unacceptable for us. I have the EPSF Version 2.0 Specification (dated Jan. 16, 1988). I noticed that the xwd2ps EPSF files have the comment "%!PS-Adobe-2.0 EPSF-1.2" instead of "%!PS-Adobe-2.0 EPSF-2.0". Could this be part of the problem? If anybody could shed some light on the problems I'm having, I'd really appreciate it. -- Thanks in advance... Scott Weitzenkamp, Talarian Corporation, Mountain View, CA uunet!talarian!scott (415) 965-8050 "Welcome to the late show, starring NULL and void" -- Men At Work