Postscript in define output
Dennis Runolfson
dennisr at fashioncarpets.com
Sun Jun 14 11:40:01 PDT 2009
Thank you,
Sorry about being vague in my question. As I indicated I have forms
defined in pcl in the output talle - and I also have some forms defined in
Prescribe - which is Brothers print formatting code. I find Prescribe to
be more intuitive then pcl.
My thought was to define any new forms in a code that would be compatible
with any new printer I use - and I was hoping postscript might be it.
It looks like since enscript not have positioning commands that would
preclude any positioning of the filepro data fields. That obviously would
be a deal breaker.
I appreciate any further comments and ideas - and thank you for pointing
out that my original question was not clear.
Dennis Runolfson
> Dennis Runolfson wrote:
>> We have several forms that we create using pcl code in the output form.
>> Can this also be done using postscript programming? If so how do you
>> tell
>> the printer to act on the instructions rather then print them?
>>
>> I have not seen this as a subject in the filepro list so I suspect it is
>> not commonly used. Any comments on how to accomplish this as well a
>> pros
>> and cons would be appreciated.
>>
>> We are running the Ubuntu version of Linux.
>>
>> Thanks in advance.
>>
>> Dennis Runolfson
>> Fashion Carpets
>
> You don't say why you want to do this. If, as Jim Asman guessed, you're
> trying to get to pdf, then his suggestion is a good one. If you want to
> print to a postscript-only printer that does not speak pcl, proper
> configuration of the printer in CUPS should allow the spooler system to
> automatically convert pcl input for output to a postscript printer. (In
> Red Hat, I always found that pcl print jobs had to begin with a reset code
> (Esc-E), followed immediately by any other escape code, in order for the
> system to recognize it as a pcl file.)
>
> If you really want to generate postscript for reasons we haven't guessed,
> you might want to look into the linux 'enscript' tool. This is a markup
> language for generating postscript output from text. It is well suited
> for use in a filepro print code table. Filepro output would be piped
> through the enscript program rather than sent directly to the spooler.
> Nice features include the ability to set font and point size, and to
> generate rules, boxes and shading, and merge graphic files (e.g.
> letterhead) into the output stream. Serious limitations include the
> absence of any positioning commands.
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
More information about the Filepro-list
mailing list