Hi,
On Tue, Oct 24, 2017 at 07:48:03PM +0200, Ingo Schwarze wrote:
> > tiff export still doesn't work).
>
> That's strange, it just works for me with the patch as you sent it,
> both for a small text-only PDF and for a large graphics-heavy PDF.
Oh, the joy of modern plugin-based software
Hi Matthias,
Matthias Kilian wrote on Mon, Oct 23, 2017 at 10:27:01PM +0200:
> tiff export still doesn't work).
That's strange, it just works for me with the patch as you sent it,
both for a small text-only PDF and for a large graphics-heavy PDF.
> For printing (using
Hi,
On Mon, Oct 23, 2017 at 06:05:08PM +0200, Alexander Bluhm wrote:
> On Sun, Oct 22, 2017 at 06:26:15PM +0200, Matthias Kilian wrote:
> > I'll try it later this evening. But I always wondered why one wants
> > to print a pdf out of a pdf *viewer* ;-)
>
> I have always used xpdf to convert the
On Mon, Oct 23, 2017 at 06:05:08PM +0200, Alexander Bluhm wrote:
> On Sun, Oct 22, 2017 at 06:26:15PM +0200, Matthias Kilian wrote:
> > I'll try it later this evening. But I always wondered why one wants
> > to print a pdf out of a pdf *viewer* ;-)
>
> I have always used xpdf to convert the
On Sun, Oct 22, 2017 at 06:26:15PM +0200, Matthias Kilian wrote:
> I'll try it later this evening. But I always wondered why one wants
> to print a pdf out of a pdf *viewer* ;-)
I have always used xpdf to convert the wanted pages to postscript
and send them with lpr to my printer. You can even
> > It does spew crap to stderr that i didn't notice with previous
> > versions, but i may have missed it. Probably such splatter is
> > to be expected with "modern" software (sigh).
> >
> > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
> > '/tmp/runtime-schwarze'
>
> I'll have to
On Sun, Oct 22, 2017 at 07:57:08PM +0200, Ingo Schwarze wrote:
> Hi Matthias,
>
> Matthias Kilian wrote on Sun, Oct 22, 2017 at 06:10:01PM +0200:
> > On Sun, Oct 22, 2017 at 12:38:09AM +0200, Ingo Schwarze wrote:
>
> >> libGL error: failed to open drm device: Permission denied
> >> libGL
On 2017/10/22 19:57, Ingo Schwarze wrote:
> Strange. I still had
>
> DisplayManager._0.setup:/etc/X11/xenodm/Xsetup_0
> DisplayManager._0.startup: /etc/X11/xenodm/GiveConsole
> DisplayManager._0.reset:/etc/X11/xenodm/TakeConsole
>
> in /etc/X11/xenodm/xenodm-config; after
On Sun Oct 22, 2017 at 07:57:08PM +0200, Ingo Schwarze wrote:
> Hi Matthias,
>
> Matthias Kilian wrote on Sun, Oct 22, 2017 at 06:10:01PM +0200:
> > On Sun, Oct 22, 2017 at 12:38:09AM +0200, Ingo Schwarze wrote:
>
> >> libGL error: failed to open drm device: Permission denied
> >> libGL
Hi Matthias,
Matthias Kilian wrote on Sun, Oct 22, 2017 at 06:10:01PM +0200:
> On Sun, Oct 22, 2017 at 12:38:09AM +0200, Ingo Schwarze wrote:
>> libGL error: failed to open drm device: Permission denied
>> libGL error: failed to load driver: i965
> Hmm. This happens if you don't own
On 2017/10/22 18:26, Matthias Kilian wrote:
> Hi,
>
> On Sun, Oct 22, 2017 at 05:03:50PM +0100, Stuart Henderson wrote:
> > It seems to have lost the ability to print. There's a build flag
> > (-DXPDFWIDGET_PRINTING=true) which might fix that, but I haven't got
> > it to build yet.
>
> I'll try
Thanks Matthias for the diff. Comments below.
On Sun Oct 22, 2017 at 06:10:01PM +0200, Matthias Kilian wrote:
> Hi Ingo,
>
> (cc'ing back to ports)
>
> On Sun, Oct 22, 2017 at 12:38:09AM +0200, Ingo Schwarze wrote:
> > > As libpaper seems fairly useless to me, i guess you might want to take
> >
Hi,
On Sun, Oct 22, 2017 at 05:03:50PM +0100, Stuart Henderson wrote:
> It seems to have lost the ability to print. There's a build flag
> (-DXPDFWIDGET_PRINTING=true) which might fix that, but I haven't got
> it to build yet.
I'll try it later this evening. But I always wondered why one wants
Hi Ingo,
(cc'ing back to ports)
On Sun, Oct 22, 2017 at 12:38:09AM +0200, Ingo Schwarze wrote:
> > As libpaper seems fairly useless to me, i guess you might want to take
> > the second approach, disable it explicitly.
> >
> > I'm now investigating how to do that...
>
> Applying the patch
On 2017/10/22 16:51, Ingo Schwarze wrote:
> Reposting here, maybe i should have done that in the first place
> to avoid duplicate work, sorry sthen@ and aja@...
Thanks :)
> It does spew crap to stderr that i didn't notice with previous
> versions, but i may have missed it. Probably such
as Kilian <k...@outback.escape.de>
Subject: Re: Update textproc/xpdf
Hi,
Ingo Schwarze wrote on Sat, Oct 21, 2017 at 11:40:15PM +0200:
> So either it has to be added as a dependency and passed to the linker,
> or it has to be disabled during cmake autoconfiguration even if it
> happens to be
On Sun, Oct 22, 2017 at 02:00:00AM +, Stuart Henderson wrote:
> On 2017/10/21 22:41, Matthias Kilian wrote:
> > Hi,
> >
> > Here's an update to xpdf-4.00.
> >
> > Now uses Qt instead of Motif :-(
> >
> > Tests and comments are welcome.
>
> I see some offsets in the patches, is that
On 2017/10/21 22:41, Matthias Kilian wrote:
> Hi,
>
> Here's an update to xpdf-4.00.
>
> Now uses Qt instead of Motif :-(
>
> Tests and comments are welcome.
I see some offsets in the patches, is that expected?
Build fails on my workstation:
xpdf/CMakeFiles/xpdf_objs.dir/GlobalParams.cc.o:
Hi,
Here's an update to xpdf-4.00.
Now uses Qt instead of Motif :-(
Tests and comments are welcome.
Ciao,
Kili
Index: Makefile
===
RCS file: /cvs/ports/textproc/xpdf/Makefile,v
retrieving revision 1.89
diff -u -p -r1.89
On Fri, May 30, 2014 at 04:37:58PM +0200, Matthias Kilian wrote:
Update to xpdf-3.04.
[...]
Tests, comments and oks are welcome.
Are only Patrick Keshishian and me using this?
Index: Makefile
===
RCS file:
On 06/07/14 22:38, Matthias Kilian wrote:
On Fri, May 30, 2014 at 04:37:58PM +0200, Matthias Kilian wrote:
Update to xpdf-3.04.
[...]
Tests, comments and oks are welcome.
Are only Patrick Keshishian and me using this?
Yes - I'd forgotten to test - it's working fine for me on amd64.
Update to xpdf-3.04.
See http://www.foolabs.com/xpdf/CHANGES for a full list of changes.
Tested with a couple of (broken and evil) pdf documents on amd64.
The fix from miod@ (dates back to 2009) shouldn't be necessary any
longer, but to be safe I prefer to keep some asserts around for a
while.
On 5/30/14, Matthias Kilian k...@outback.escape.de wrote:
Update to xpdf-3.04.
See http://www.foolabs.com/xpdf/CHANGES for a full list of changes.
Tested with a couple of (broken and evil) pdf documents on amd64.
The fix from miod@ (dates back to 2009) shouldn't be necessary any
longer,
On Fri, May 30, 2014 at 10:26:50AM -0700, patrick keshishian wrote:
The fix from miod@ (dates back to 2009) shouldn't be necessary any
longer, but to be safe I prefer to keep some asserts around for a
while.
Are there test-cases which can be shared?
Miod mentioned this one, but the
On Sun, Sep 11, 2011 at 08:19:55PM -0700, patrick keshishian wrote:
Hmm... I am trying to build xpdf but looks like
patches/patch-splash_SplashXPathScanner_cc does not apply correctly.
It has been removed. You forgot to run patch(1) with -E.
Ciao,
Kili
On Mon, Sep 12, 2011 at 11:10 AM, Matthias Kilian
k...@outback.escape.de wrote:
On Sun, Sep 11, 2011 at 08:19:55PM -0700, patrick keshishian wrote:
Hmm... I am trying to build xpdf but looks like
patches/patch-splash_SplashXPathScanner_cc does not apply correctly.
It has been removed. You
On Thu, Sep 8, 2011 at 2:59 PM, Matthias Kilian k...@outback.escape.de wrote:
On Tue, Sep 06, 2011 at 07:39:53PM -0500, Amit Kulkarni wrote:
I checked this out... working fine on amd64. everything okay.
Thanks for testing. I'll commit it in two weeks if nobody gives any
negative report.
On Sun, Sep 11, 2011 at 8:19 PM, patrick keshishian pkesh...@gmail.com wrote:
On Thu, Sep 8, 2011 at 2:59 PM, Matthias Kilian k...@outback.escape.de
wrote:
On Tue, Sep 06, 2011 at 07:39:53PM -0500, Amit Kulkarni wrote:
I checked this out... working fine on amd64. everything okay.
Thanks for
On Tue, Sep 06, 2011 at 07:39:53PM -0500, Amit Kulkarni wrote:
I checked this out... working fine on amd64. everything okay.
Thanks for testing. I'll commit it in two weeks if nobody gives any
negative report.
Ciao,
Kili
I checked this out... working fine on amd64. everything okay.
thanks
On Tue, Sep 6, 2011 at 2:49 PM, Matthias Kilian k...@outback.escape.de wrote:
Anyone? Only edd@ reported back until now.
On Sun, Aug 21, 2011 at 08:51:20PM +0200, Matthias Kilian wrote:
I removed PKGNAME-main by accident.
I removed PKGNAME-main by accident. Please use this diff instead
of the one i sent last friday.
Index: Makefile
===
RCS file: /cvs/ports/textproc/xpdf/Makefile,v
retrieving revision 1.79
diff -u -p -r1.79 Makefile
--- Makefile10
Update to xpd-3.03.
Please test this to death, comment, ok ;-)
About the removed patches: some of them have been included upstream,
sometimes not completely obvious (because upstream did some
refucktoring). Two removed patches that aren't obvious at all are
patch-xpdf_Catalog_cc and
Update to xpdf 3.02pl5 (which simply applies fixes for CVE-2010-3702 and
CVE-2010-3704), and update the splash/SplashXPath.cc bounds checking fix
to survive yet another killer pdf
(ATT2100_Microprocessor_Hardware_Specification_Mar91.pdf from bitsavers,
if you're curious; xpdf would dump core when
Update to xpdf 3.02pl5 (which simply applies fixes for CVE-2010-3702 and
CVE-2010-3704), and update the splash/SplashXPath.cc bounds checking fix
to survive yet another killer pdf
(ATT2100_Microprocessor_Hardware_Specification_Mar91.pdf from bitsavers,
if you're curious; xpdf would dump core
34 matches
Mail list logo
