comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: Importing IDL Postscript output into Windows apps
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Importing IDL Postscript output into Windows apps [message #5374 is a reply to message #5368] Thu, 30 November 1995 00:00 Go to previous messageGo to previous message
Liam Gumley is currently offline  Liam Gumley
Messages: 473
Registered: November 1994
Senior Member
Well it appears that I was a bit hasty in claiming that IDL postscript
output could not be imported successfully into Word for Windows 6.0.

In fact, single page IDL postscript files (created with or without the
/encapsulated keyword) can be imported into Word for Windows 6.0 just fine,
using "Insert, Picture". However it should be noted that a preview image is
*not* displayed in Word. Further, Word does not recognize the preview image
generated when you use the /preview keyword in IDL. More on preview images
later.....

Anyway, my problem was that I was not using the "Postscript Printer" driver
in Word for Windows, as was pointed out to me by Jun Tan (j.tan@rl.ac.uk).
The correct driver file name is PSCRPT.DRV, and it can be installed under
the Windows Control Panel Printers option.

So in short, to import IDL postscript into Word for Windows 6.0:
(1) Create the postscript file in IDL. Use of the /encapsulated keyword is
optional. Do not use the /preview keyword.
(2) Import the picture into Word using "Insert, Picture".
(3) Ensure that you are using the "Postscript Printer" driver in Word.
You can check this by looking at the "Printer: " identifier shown at
the top of the dialog box opened when you select "File, Print".

As long as you have a generic postscript printer, this procedure should
work just fine. We still have some unresolved problems with our HP Laserjet 4
printer when trying to print postscript images created using the /color keyword
in IDL that are imported into Word 6.0 documents. However I think this is
purely a printer problem.

Now to the subject of preview images. According to Mark Hadfield
(hadfield@storm.greta.cri.nz):
(start of quoted text)
MS Word will recognise preview bitmaps in TIFF and WMF forms, but not the
"device-independent" form that's added by the IDL /PREVIEW switch.

I know of two command-line tools that are supposed to add TIFF previews. These are
ps2epsf (available for Unix machines) and epstool (available for Unix, OS/2 &
Windows). I haven't managed to get either to work.

I add bitmap previews to all my EPS files using GSview, a Windows front-end to
Ghostscript. The procedure is a little tedious (you to make 3-4 menu selections &
enter a file name, also ensure you have selected several options appropriately) so I
wrote a Visual Basic front-end program that drives it. Like I said, not simple, but
it works. It works sufficiently well that I make all my graphs in EPS + preview form
and collect them inside Word documents.
(end of quoted text)

Like Mark, I spent some time trying to get ps2epsf and epstool to work. Due to
some version problems with ghostscript, I was unable to get them to work.
However, I did come up with a procedure that uses ghostscript, ImageMagick, and
NetPBM tools to add TIFF preview images to IDL postscript files, which can
then be imported into Word for Windows 6.0. As soon as I have fully tested and
debugged this approach, I'll post instructions.

Finally, I'm sorry if all this appears quite obvious. Our little IDL users group
here at UW has been trying to figure this out for some time.

Cheers,
Liam.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: IDL 4.0.1 reading problem?
Next Topic: Re: IDL Survey Comments

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 19:34:05 PDT 2025

Total time taken to generate the page: 0.00428 seconds