Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: Implementation of "Print on Form" in CUPS for PostScript printers ("execform" in PS) #66

Closed
michaelrsweet opened this issue May 2, 2003 · 2 comments
Labels
duplicate This issue or pull request already exists enhancement New feature or request
Milestone

Comments

@michaelrsweet
Copy link
Collaborator

Version: 1.2-current
CUPS.org User: pipitas


General Feature Request (II):

           CUPS is missing an option to "print on forms". This 
       print option is more and more in demand in the Windows
       world. (It is used to print business letters without
       bothering to insert the business paper into the
       printer, etc...)  -- PostScript has an operator 
       "execform" which allows the implementation of features
       like printing on forms, create an optimized workflow
       for serialized/personlized letters etc, by first 
       loading the invariable data (the "form") into the
       interpreter, and then send the variable data separately
       (with a call to print on the stored form).

Questions: Does Ghostscript support the "execform" feature?
---------  What is its performance? Is it conceivable that a CUPS 
           or ESP Print Pro implementation is made which uses this?

       Long ago, I noticed the MIME type recognition rules for 
       "application/vnd.cups-form". So you seem to have (had?)
       plans to work on that "print on forms" feature somehow.
       What are your current plans with that?

Cheers,
Kurt

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

First, the PostScript execform stuff might have some application with the form/overlay functionality we'll be adding; there are some serious limitations in the size of files that can be embedded using this operator, however, so I'm not sure if it will be a perfect fit...

Second, the application/vnd.cups-form MIME type (as defined in the IDD) is an XML format for automated form completion; basically you'd use an XML file, a preprinted form or a form "background" file, and some data to compose one or more pages. The form filter for this MIME type was never written and probably will be removed as it turns out it is easier to implement in the client then in the server.

Third, forms extend beyond templates - we also want to have a way to map predefined form names to InputSlot and PageSize options on a per-queue basis, with a way to fall back on blank paper and a form background file...

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

BTW, this falls under STR #65...

@michaelrsweet michaelrsweet added enhancement New feature or request duplicate This issue or pull request already exists labels Mar 17, 2016
@michaelrsweet michaelrsweet added this to the Stable milestone Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant