-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add support for orientation option #2
Conversation
I'm not so surprised this has no effect. Asking raster printers to transform the page seems rather orthogonal with that they may require the client to help transform duplex backsides. As i understand it, this is to not need to have the entire uncompressed raster in RAM. Needing to do rotation for you would negate that optimization. (And i see several printers that need said help, but still supposedly support other orientations. Even including needing backsides rotated for it but claiming support for reverse portrait in IPP). So, similar to attributes related to backside-transform, it could well be one of those attributes where you describe what you have done to the document data, rather than what you want the printer to do with it. The standard (cs-ippraster) is not very clear on what this is though. RFC 8011 says the corresponding IPP attribute specifically has nothing to do with what you send to the printer, just how you want it printed. But i guess that could just mean that it, like copies, is one of those things to "move" from IPP to the PWG raster header. Ipptransform doesn't seem to do anything with it outside of number-up. Maybe it's a dead setting? But i'm curious, why would you want your document to come out long-side-first? I know sometimes this is done, though i can't help but feel it is just a waste of maximum paper size that can be used. I also see you still keep your now-obsolete commits - if there is something wrong with what i did, do tell me. |
Thanks for commenting @attah that's really helpful.
We have preprinted media and have found that flipping on the long edge is required in some cases to align the printed front with the back.
No not at all. We plan on switching back to the upstream as soon as we schedule some updates on our device fleet 👍🏻. Our fork has some code to maintain support with an older poppler version which can become a pain when bringing in upstream changes that use newer poppler features. |
Also we have found this |
As in that the printer does a better job with alignment if pages are fed like this?
Pretty cool that it's in production already!
That's the same standard i meant. It is mentioned, but also doesn't really say what it does (though it seems mandated for compliance). Could be that you need to set the feed orientation too. With some more thought, since the backside transformations are defined in feed and cross-feed directions, but refer directly to duplex/tumble which is defined in long and short sides... then i don't see any room for non-portrait orientations actually working. I probably should ask the PWG folks. |
This reverts commit fd1d97c.
I haven't had any success with this, or I had assumed that |
Correct. I wasn't considering bulk manual duplex. Anyway, i asked the PWG folks what this is supposed to work like. No answer yet. |
I heard back. :) Apparently the design requirement of no printer-side transforms needed does not apply here. Anyway - does that sound like what you wanted to do? |
good to know 👍🏻 I think upon further inspection with our operations team this "flip" doesn't actually need to happen, and we can adjust how print media is loaded like you alluded to earlier 👍🏻 thanks |
This embeds the
Orientation
value in the PWG header, but it seemingly has no effect (at least on the Epson printer I've specified). However, it is definitely being embedded so this could be a quirk with the printer.