(no subject)
Anton Thomasson via ipp <[email protected]>
| Newsgroups | gmane.ietf.ipp |
|---|---|
| Message-ID | <CABFDNXTXb6PfxHvabrQuUFYRAC+mFGo==f6SH12ZV8jNtcgwxA@mail.gmail.com> |
Hi (Seems i had fallen off the list somehow, so re-sending after re-registering, sorry if ends up going out twice). I was reminded that there is an Orientation setting in the PWG raster page header, but unfortunately the spec doesn't say much about how it is to be used. One interpretation could be that it requests the printer to transform the page as requested, but that would go against Design Requirement 2. So presumably, like the transform fields, it is more of a description of what the client has done to the page bitmap. Is that the correct interpretation? Is this the Orientation referred to in 6.4 c, or is that backside transformation, or both? Landscape output doesn't seem very popular... but achieving full compliance would be pretty neat. Something that has me puzzled though is how Orientation relates to the Transform values. Table 9 has a neat reference on what to do to back pages when the printer needs help transforming them, but it defines the transforms in cross-feed and feed, *and* refers directly to duplex/tumble which are edge-length-based. Is there a dimension missing in the table to account for orientations? I.e. if the printer is to output Landscape, Long/Short Edges are now different relative to the feed direction compared to normal. For "rotated", which seems most common, the table says "unless you want it two-sided around the short edge (usually the feed direction) rotate it for me". But surely the printer's need for help stays the same relative to the feed direction, so now if a long edge is towards the feed direction, the when to rotate should switch, or? How does this relate to LeadingEdge BTW - just keep them in sync? Br, Anton _______________________________________________ ipp mailing list [email protected] https://www.pwg.org/mailman/listinfo/ipp