<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Make printjob a background process and replace they print dialog with an icon in status bar" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138542#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Make printjob a background process and replace they print dialog with an icon in status bar" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138542">bug 138542</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Michael Weghorn from <a href="show_bug.cgi?id=138542#c5">comment #5</a>) > (In reply to Michael Weghorn from <a href="show_bug.cgi?id=138542#c3">comment #3</a>) > > What happens at least on Linux is basically: > > [...] > > Just to emphasize that: My <a href="show_bug.cgi?id=138542#c3">comment 3</a> was actually for Linux. Windows (and > it's printing system) may well be a completely different thing. I fear so, sadly :P. I personally preference/ideal as much shared code/ behavior as possible.. If a PDF is generated under Linux and send to cups, maybe similar approach could be used under Windows (except the cups part of course). @Offtopic There are currently to many discrepancy with different back-ends (Skia/GDI/QT/GTK3), printing (in this case) or epub (slow under windows, not Linux). Now Linux/Mac users are complaining about image perf issues (previously a Windows issue), now gone under Windows (thanks to Skia). But reshuffling bugs not really helpful. And with some bad luck the fix for solving the perf issue under Linux/Mac will bring back issues for Windows/Skia (Raster and/or Vulkan)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>