Summary: | Wrong order when printing multiple pages on 1 paper with "reverse" enabled | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kdelibs | Reporter: | patrick.schwalm |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | jlayt |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
patrick.schwalm
2009-01-16 16:12:09 UTC
Printing n-up is done using the standard CUPS options which we support by adding tabs to the Qt print dialog, so it's not an Okular or Qt issue. Reassigning to KDEPrint as the best place for this. I need to read the report properly to understand the point, but it is one of a number of bugs filed to do with the page ordering during n-up in both KDE3 and 4, most seem to involve being combined with non-standard print options, e.g. landscape or reverse order. Could be an issue with CUPS, or just that users need to change the page order option to match the other chosen options, in which case we could be more intelligent in the UI to help set the options up. That's going to need some investigation and thinking. Ah, I understand. We apply the reverse setting to the page order as they get laid put on the paper, while the reporter would like it applied to the paper order as it comes out of the printer instead. Hmmm. Both options are equally valid results, indeed both at the same time would be valid, although the second can be manually achieved after printing. We should look for a way to provide both. I'll look see what order of precedence CUPS applies the n-up and reverse filters in its workflow, we may be able to apply the CUPS command to achieve this by providing an extra. Thank you very much. I think the combination of my bad english and the topic was not really easy to read... but your did describe it right in the last topic... Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |