https://bugs.documentfoundation.org/show_bug.cgi?id=164354

--- Comment #11 from Patrick (volunteer) <[email protected]> ---
(In reply to James R from comment #10)
> The print dialog opens at the expected speed. But the double-sided print
> setting appears to be being ignored. (Bug
> https://bugs.documentfoundation.org/show_bug.cgi?id=163126 is still present,
> but that was to be expected.)

That is pretty strange that double-sided printing is ignored. I assume that
double-sided is a post-processing step done by your printer's print driver
(although I think some print drivers are bundled with macOS).

My understanding of macOS printing is there a pipeline of steps and each step
is handled by separate LibreOffice, macOS, or print driver code:

1. LibreOffice requests macOS to start a print job.
2. macOS creates a temporary PDF and LibreOffice adds the document's contents
to the PDF. Note: this is the step where my fix for this bug was implemented.
We are now adding content to the PDF faster.
3. macOS displays the native print dialog and displays the PDF in the sidepane
on the left.
4. If you then change any of the print settings (except those in the
"LibreOffice" section), macOS does some post processing on the PDF. For
example, changing Layout > Pages per Sheet causes macOS to immediately
post-process the PDF and update the sidebar on the left.
5. Finally, if you actually send the output to a printer, post processing is
done by the print driver for things like double-sided since PDF has no concept
of double-sided. PDF is just a list of pages.

Unfortunately, my print driver (I only have the RWTS "print to PDF file"
printer) does not support double-sided so macOS hides that print dialog section
when I print.

So does double-sided work in NeoOffice if you use the same print dialog
settings as in LibreOffice? If so, then maybe there is some hope that the bug
is in the LibreOffice code. Of course, then the bigger mystery is how is
LibreOffice able to influence a print driver post processing step.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to