filter/rastertohp: fix short-edge (Tumble) duplex mode - #1704
Open
NishizakiHayato wants to merge 1 commit into
Open
NishizakiHayato wants to merge 1 commit into
NishizakiHayato wants to merge 1 commit into
Conversation
'1 + header->Tumble != 0' parses as '(1 + header->Tumble) != 0' and is always 1, so ESC&l2S was never sent and short-edge jobs printed long-edge. Add the missing parentheses.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
'1 + header->Tumble != 0' parses as '(1 + header->Tumble) != 0' and is always 1, so ESC&l2S was never sent and short-edge jobs printed long-edge. Add the missing parentheses.
When I was using the Generic PCL Laser Printer driver from China Kylin Linux to control my printer, I encountered a problem where even though I selected short edge flipping for double-sided printing, the printer still flipped on the long edge. After investigating with AI, I discovered this error and applied a corrected driver. The results showed that the corrected driver worked as expected.
https://www.netlab.ac.cn/post/14.html