If old Qt3 wrapper of poppler is separated as an individual source package and self-standing autoconf is included, it will serve for the people sticking to KDE3? I will be able to do such. I'm afraid KDE people prefers cmake, but I have no skill for it.
I have to note that Qt3 wrapper is dropped during 0.16.x API, so its original source does not match with the latest poppler 0.17.x (Link and AnnotLink are merged on 2011-Mar-01). The current mismatch is so small and easy to fix (I could do it), but nobody can guarantee that next mismatch would be small again (if big, I won't do, because I'm not KDE user so I cannot test at all). I'm questionable whether KDE3 community have sufficient human resource to investigate the mismatch and fix them continuously. As Albert already pointed out, using older/unmaintained source would be stable solution, if no human resource for such work is unavailable in KDE3 community. Regards, mpsuzuki Ilya Chernykh wrote: > On Saturday 17 September 2011 06:31:42 Brad Hards wrote: > >>> I saw your January post where you asked whether anybody needs poppler-qt3, >>> but unfortunately the people who actually need it were not subscribed to >>> the list at that moment. >> Who actually needs it? >> >> It seems like the trinity project isn't doing 6 monthly releases any more >> (last release was almost a year ago), and even in KDE3 we didn't use poppler >> for anything critical. > > It is used for PDF import/export in koffice. > _______________________________________________ > poppler mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/poppler _______________________________________________ poppler mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/poppler
