Dear people from Gentoo, I am a Debian Maintainer and I regularly use xpdf. I see that you have taken the task of maintainance of xpdf with the poppler backend as some patches and I would like to take things further. Part (but only part) of my motivation comes from here: <http://rb.doesntexist.org/blog/2010/05/27/please-let-me-zoom-my-documents/>. Since I am already integrating some of your patches in my git tree, it would only be a logical to invite you to take advantage of it: http://github.com/rbrito/xpdf-poppler I would like to ask your help keeping things in shape (and adapting it whenever newer poppler versions arrive, that make API changes), so that we can all benefit from that and avoid duplicated efforts. I also plan on doing a plan on doing some housekeeping, eliminating unnecessary, legacy code that only serves the purpose of providing abstraction layers which we are not be using and which only complicates the code. Hope to hear from you soon, Rogério Brito. Reproducible: Always
I don't see this used in Debian yet (re: http://packages.debian.org/sid/xpdf) but I like the idea, moving to xpdf & poppler maintainers...
(In reply to comment #1) > I don't see this used in Debian yet (re: http://packages.debian.org/sid/xpdf) Yes, it is not there, basically because some people objected to it. You can see the discussion at (and posts around it): http://lists.debian.org/debian-mentors/2010/06/msg00047.html On the other hand, people from the security team of Debian have expressed satisfaction with this project: http://lists.debian.org/debian-mentors/2010/06/msg00159.html > but I like the idea, moving to xpdf & poppler maintainers... Regardless of this being adopted in Debian, I am willing to work hard on this project and I think that we can leverage on the improvements that are being made to poppler, since the xpdf development itself has mostly stagnated. Thanks.
I also like the idea; we already switched all our TeX stuff to (shared) poppler instead of (static) xpdf. However, I can't get my way into github, have you released any tarball yet ? (I mean a tarball, signed & everything, not a .tar.gz generated from a vcs)
(In reply to comment #3) > I also like the idea; we already switched all our TeX stuff to (shared) poppler > instead of (static) xpdf. However, I can't get my way into github, have you > released any tarball yet ? (I mean a tarball, signed & everything, not a > .tar.gz generated from a vcs) No, not *yet*, but I may be doing that soon. In fact, I may be doing that sooner if I know that, perhaps, any distribution (say, Gentoo) is going to use it. :-) Regards, Rogério Brito.
(In reply to comment #4) > (In reply to comment #3) > > I also like the idea; we already switched all our TeX stuff to (shared) poppler > > instead of (static) xpdf. However, I can't get my way into github, have you > > released any tarball yet ? (I mean a tarball, signed & everything, not a > > .tar.gz generated from a vcs) > > No, not *yet*, but I may be doing that soon. In fact, I may be doing that > sooner if I know that, perhaps, any distribution (say, Gentoo) is going to use > it. :-) Speaking only for myself, I am interested in such a project and could add it to the tree and maintain it. At the beginning, there will be both xpdf and xpdf-poppler in our tree, when everyone will be happy with xpdf-poppler, we can rethink about it and kill the old xpdf. Anyway, what we have at the moment is a homemade xpdf-poppler...
Added basic live app-text/xpdf ebuild. So people can help with development of the thingie. Some things for sure needs to be adjusted before releasing some nice tarball :) Cheers
Hi Rogério, what's the status here, is there any chance of a release in the near future? Cheers, Andreas
Removed from the tree for now.