Having been working on the move away from libkdeprint and to relying almost entirely on Qt’s printing framework, it’s become clear to people the power of Michael Goffioul’s creation. Unfortunately, the only people who understand the code base, as far as I can see, are Michael himself (who has moved on to other projects) and the maintainer, Cristian Tibirna, who doesn’t have enough time available to port the library (a none-trivial task, given the size and complexity of the library and the fact that it is supposed to work as a drop-in replacement for QPrinter, which has had significant API changes).
There has been much wailing and gnashing of teeth over its removal. Just yesterday I wanted to print a booklet from Scribus, and so went looking on the internet for how to do it. A page on Scribus’ wiki told how to do it using the kprinter utility. It was a really simple task, as well, although the way I’d done it meant made it a little more complicated (I had made the pages the final size – A5 – rather than twice the original size, which requires an extra parameter to the psnup utility).
Perhaps people with the time (ie: not Cristian) and expertise (ie: not me) will cause it to make a triumphant return. Perhaps advancements in Qt’s own printing system will make it unnecessary. We shall see. Certainly, some of it needs to be salvaged for the printing kcm and for a kprinter utility. I suspect Qt will never have a “printFiles()” method that will take postscript or pdf files and print them, if only because it’s hard to implement on Windows. In fact, really the only way to do it that I can see is to take the same path as Scribus and use Ghostscript.
As KDE’s resident printing guru (Kurt Pfeifle) has commented before, printing is one of those things that is not sexy (and so doesn’t get worked on) but is necessary and really noticed by the user if it is below par. And, indeed, if it is exceptional, as KDE’s has been up to now.