You may want to look at Pdftk at http://www.pdflabs.com/.
You may be able to use Pdftk to massage the pdf file you can open it.
I don't know if it will build on OpenBSD (although there is a FreeBSD port.)
Regards,
On 12/07/10 03:47, Sebastian Reitenbach wrote:
On Tuesday 07 December 2010 08:
On Tuesday 07 December 2010 08:40:01 am Clint Pachl wrote:
> Anthony Bentley wrote:
> >> This happens when there are multiple PDFs embedded in a single PDF file.
> >> I remember reading a Ghostscript bug about this (could probably find it
> >> again if I had the exact error message), but unfortunat
Anthony Bentley wrote:
This happens when there are multiple PDFs embedded in a single PDF file.
I remember reading a Ghostscript bug about this (could probably find it
again if I had the exact error message), but unfortunately Mupdf still
doesn't support it.
Here is the Ghostscript bug:
ht
ropers wrote:
On 6 December 2010 22:42, Clint Pachl wrote:
Still get a single page PDF stating the above message.
I guess it has to do with this PDF being a portfolio, like Anthony Bentley
mentioned.
How are the constituent PDFs stored in the portfolio PDF? Unencrypted?
pdfinf
On 6 December 2010 22:42, Clint Pachl wrote:
> Still get a single page PDF stating the above message.
>
> I guess it has to do with this PDF being a portfolio, like Anthony Bentley
> mentioned.
How are the constituent PDFs stored in the portfolio PDF? Unencrypted?
Would it be possible to simply u
2010/12/6 Clint Pachl :
> mentions a possible hack. okular apparently uses poppler as the backend.
> Poppler is a fork of xpdf-3.0, so we're back to square one.
To quote the mailing list motto: Stop whining. Where's the patch? ;-}
I can find no bug report in the podofo bugzilla.
Best
Martin
Joel Wiramu Pauling wrote:
I would be surprised if okular didn't open it. (okular being the KDE viewer)
I don't have KDE so I can't test. But I did find this link:
http://forum.kde.org/viewtopic.php?f=20&t=91242
It looks like portfolio PDFs are not supported, although someone there
menti
> This happens when there are multiple PDFs embedded in a single PDF file.
> I remember reading a Ghostscript bug about this (could probably find it
> again if I had the exact error message), but unfortunately Mupdf still
> doesn't support it.
Here is the Ghostscript bug:
http://bugs.ghostscript.c
I would be surprised if okular didn't open it. (okular being the KDE viewer)
On 7 December 2010 10:42, Clint Pachl wrote:
> Joachim Schipper wrote:
>>
>> On Sat, Dec 04, 2010 at 06:28:04PM -0700, Clint Pachl wrote:
>>
>>>
>>> When I open [the UPS developer's guide] with xpdf(1) I get a [message]
Joachim Schipper wrote:
On Sat, Dec 04, 2010 at 06:28:04PM -0700, Clint Pachl wrote:
When I open [the UPS developer's guide] with xpdf(1) I get a [message]
to download the the latest Adobe crapware to view it.
This is cheating, but have you tried throwing it into Google docs?
On Sat, Dec 04, 2010 at 06:28:04PM -0700, Clint Pachl wrote:
> When I open [the UPS developer's guide] with xpdf(1) I get a [message]
> to download the the latest Adobe crapware to view it.
This is cheating, but have you tried throwing it into Google docs?
Joachim
On 2010-12-05, Brynet wrote:
> Hi,
>
> Why are you using xpdf? it's so old and crummy :-).
>
> print/epdfview, which uses the poppler library.
AFAIK the poppler library is based on xpdf code so the result would be
about the same.
Best regards,
Jona
--
Worse is better
Richard P. Gabriel
On Sat, 4 Dec 2010, Abel Abraham Camarillo Ojeda wrote:
On Sat, Dec 4, 2010 at 8:17 PM, Brynet wrote:
Hi,
Why are you using xpdf? it's so old and crummy :-).
print/epdfview, which uses the poppler library.
textproc/mupdf, independent renderer, pretty good.
-Bryan.
There is also textproc
On 12/04/10 23:09, Clint Pachl wrote:
> All I can say is that I use cwm and don't like interfaces, GTK, gnome,
> or KDE. I highly agree with Patrick.
I also use cwm, but that doesn't means I completely avoid applications
using GTK+ or even Qt, there aren't a whole lot of programs using xlib
or xcb
Brynet wrote:
Hi,
Why are you using xpdf? it's so old and crummy :-).
print/epdfview, which uses the poppler library.
textproc/mupdf, independent renderer, pretty good.
-Bryan.
All I can say is that I use cwm and don't like interfaces, GTK, gnome,
or KDE. I highly agree with Patrick.
On Sat, Dec 4, 2010 at 8:17 PM, Brynet wrote:
> Hi,
>
> Why are you using xpdf? it's so old and crummy :-).
>
> print/epdfview, which uses the poppler library.
> textproc/mupdf, independent renderer, pretty good.
>
> -Bryan.
>
>
There is also textproc/zathura.
On Sat, Dec 4, 2010 at 6:17 PM, Brynet wrote:
> Hi,
>
> Why are you using xpdf? it's so old and crummy :-)
Not addressed to me, but my opinions below.
> print/epdfview, which uses the poppler library.
I haven't tried this, but I'm not a fan of GTK apps. most are fugly and clunky.
> textproc/m
Hi,
Why are you using xpdf? it's so old and crummy :-).
print/epdfview, which uses the poppler library.
textproc/mupdf, independent renderer, pretty good.
-Bryan.
> UPS is so annoying. The UPS developer's guide is in a 9MB PDF file. When
> I open it with xpdf(1) I get a (1) page PDF that states I need to
> download the the latest Adobe crapware to view it.
>
> How can I get around this? Why does xpdf even abide?
>
> I tried the following gs(1) command hoping
19 matches
Mail list logo
