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

Extend CUPS banner format (application/vnd.cups-banner) to allow background/foreground PDF template #5460

Open
KurtPfeifle opened this Issue Dec 11, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@KurtPfeifle
Copy link

KurtPfeifle commented Dec 11, 2018

The current application/vnd.cups-banner file format specification does not allow for much customization by users.

It consists of lines with initial keywords Header, Footer, Show, Notice and Image with additional values or variables to describe elements which should appear on the printed banner page.

I as well as at least some other users would like to extend that format by at least one keyword: Background, which should indicate a "template" PDF to be used as the background for the complete page, onto which the other elements of the banner would then be "stamped"...

If it is not too much of an effort the same could be done for keyword Foreground (which would point to a foreground PDF that would be overlayed on top of the other content).

This functions should be similar to what the command line tool pdftk would achieve by running pdftk original-banner.pdf background banner-background.pdf output new-banner.pdf


(Of course, the various x-bannertopdf filters, CUPS' own as well as third-party ones, also need to be extended so they understand this new keyword [or simply ignore it if they don't know what it means]).

@michaelrsweet michaelrsweet self-assigned this Dec 13, 2018

@michaelrsweet michaelrsweet added this to the Future milestone Dec 13, 2018

@michaelrsweet

This comment has been minimized.

Copy link
Collaborator

michaelrsweet commented Dec 13, 2018

I don't see us extending the format at this point, but will hold for possible future use...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment