Version: 0.13.2 (using KDE 3.1.4) Installed from: compiled sources Compiler: gcc version 3.2.3 OS: Linux (i686) release 2.4.20 I downloaded a pdf file from the internet and opened it with kghostview,but it showed only blank sheets of paper.I opened it with xpdf and saw the real contents of the file. It seems strange to me,but that bug only happens with this exact file.It is about 250 k. and if you wish I can send it.
Subject: Re: New: kghostview will open a .pdf file and show it empty Le Tuesday 25 November 2003 00:28, vous avez
Here goes the link : http://www.bnr2.org/BNR2BeginnersGuide(beta11.4).pdf
I am sorry, it works for me on several versions of kghostview (including HEAD and 3.1.4 which you reported against). Does it fail every time? What if you download the file to your hard disk first? Do you know what version of gs you are running (try "gs --version" on a terminal)? thanks, luis
Yes,every time I open the file I get blank sheets of paper.I downloaded the file and opened it from the disk,but the problem was still there. My version of gs is 7.05.6 and it came with my slack. BTW that's the only file I cannot open with kghostview.
It didn't display the quanta and kdevelop sheets ... here's the link http://www.sourcextreme.com/presentations/quanta.pdf I'm using 3.2RC1 but it displays weel with kpdf !!!
For the quanta link, the problem is ghostscript, not kghostview. And I cannot do anything about that, sorry. (the first link still works flawlessly for me, so I can't really "fix" it).
You are probably missing fonts. I had the same problem as you, and i downloaded fonts, and now, i cans this file properly. Try download theses files ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/fonts/ghostscript-fonts-std-8.11.tar.gz http://ftp.gnu.org/pub/gnu/ghostscript/gnu-gs-fonts-other-6.0.tar.gz And unpack them in /usr/share/ghostscript
Does it happen with Okular? That is, does Okular warn you abot the lack of fonts needed for the document, or does it just show blank pages as KGhostView used to?
I've just tested it with Okular 0.14.3 and the problem seems to be gone - no warning is shown and the document is fully loaded. Please change the status of the issue as needed, I believe it should be mark as fixed, but I'm not sure, so I'll leave it in the current status.