On Tuesday 17 May 2011 02:47:07 John E. Perry wrote:
So, I read through the history of the bug; rather than contribute to the acrimony on bugzilla, I'll just note here that at least two okular developers are presently looking at the problem (as of May 8), which seems to be due to a serious lack of attention to the overall kde printing code for many years, now, culminating in the loss of a system-level printing facility (since the thoroughly obsolete kde3 code doesn't work under kde4).
This forces application developers to do their own thing at the application level, which many are justifiably unwilling to do, since it makes system-level people less eager to do the hard stuff that's really needed.
Do I understand it correctly, kde folks? I base the above on half-understood comments of Stefan, Francesco, Albert, and Falk, plus a couple of end users who seem to be fairly well connected.
Only partly, see my explanation in a separate thread on the KDE printing situation. In Okular things are complicated by not actually using Qt to send print jobs to Cups as Qt doesn't support file printing and we want to use the original source file for best possible quality output I've poked a stick at this bug a couple of times to try figure it out and it's hard to pin down whether its Okular, Poppler, or CUPS that is getting the setting so wrong. It also only happens for me in certain PDF's so it's somewhere between what the PDF says, how Poppler interprets that, how Okular then passes that to Cups and how Cups then interprets that. We've tried patching it a couple of times in Okular, but the knock-on effect of changing the value caused even worse problems to appear so we reverted. With all the heat and light surrounding this one I'll admit to deliberatly not getting involved any further. John. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org