Re: Problems with using {PRINT} to send Postscript commands...
From: Greg Mouning (greg.mouning_at_yale.edu)
Date: 06/09/04
- Next message: Suzanne S. Barnhill: "Re: Linked text boxes containing tables"
- Previous message: Jezebel: "Re: jumping text while typing"
- In reply to: Jezebel: "Re: Problems with using {PRINT} to send Postscript commands..."
- Next in thread: Jezebel: "Re: Problems with using {PRINT} to send Postscript commands..."
- Reply: Jezebel: "Re: Problems with using {PRINT} to send Postscript commands..."
- Messages sorted by: [ date ] [ thread ]
Date: 9 Jun 2004 15:12:37 -0700
Hi Jezebel,
Thanks for the tip on how to generate valid EPS files. My particular
project involves both postscript and EPS together. I learned through
another postscript bulletin board that it is possible to cache an EPS
file in the printer memory or on a network printer hard drive and when
I'm ready, I can call it to be executed. This method is suppose to
make printing to postscript printers more efficient. Can you or anyone
listening out there explain how this is done? As you can see, this
means I will need to know how to submit valid postscript code from
within MS Word.
Many thanks for any advice you have.
Regards,
Greg
"Jezebel" <dwarves@heaven.com.kr> wrote in message news:<ev$VQzaTEHA.332@TK2MSFTNGP11.phx.gbl>...
> Yes, certainly you can do that, and indeed that's the main purpose of the
> PRINT command. The problem is that the sample you posted is not a
> well-formed EPS file. Check Google for any number of references to the
> specification. In particular ....
>
> QUOTE
> At a minimum, it must include a header comment, %!PS-Adobe-3.0 EPSF-3.0, and
> a bounding box comment, %%BoundingBox: llx lly urx ury, that describes the
> bounds of the illustration. (The specification does not require the EPSF
> version, but many programs will reject a file that does not have it.)
> UNQUOTE
>
> It must surely be a very complex letterhead for this to be a good approach.
> With most publishing applications, a simpler method is to select the
> letterhead in the original and save as a GIF, then import that into Word --
> with the added advantage that you can actually see what you're going to get,
> you're more likely to get a usable output printing to PDF, and you can email
> your correspondence users without a PostScript printer.
>
- Next message: Suzanne S. Barnhill: "Re: Linked text boxes containing tables"
- Previous message: Jezebel: "Re: jumping text while typing"
- In reply to: Jezebel: "Re: Problems with using {PRINT} to send Postscript commands..."
- Next in thread: Jezebel: "Re: Problems with using {PRINT} to send Postscript commands..."
- Reply: Jezebel: "Re: Problems with using {PRINT} to send Postscript commands..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
