OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: desertrat on April 04, 2006, 02:59:32 am
-
Has anyone else noticed that xpdf (I'm using 1.1.0beta1, rc12 had the same problem) cuts off the right side and bottom of the page. See screenshots.
[ You are not allowed to view attachments ]
here is what page looks like in kpdf
[ You are not allowed to view attachments ]
xpdf on pdaXrom, note the text is cut, the keyboard and the mouse is missing. NB changing the zoom doesn't rectify the problem, it just cuts off varying amounts.
BTW xpdf on Pocket Workstation doesn't have this problem. Any ideas?
-- cheers
-
I noticed that, but it doesn't seem to do it in portrait rather than landscape mode on my C1000
-
And if I move xpdf to a different virtual screen it helps sometimes.
-
No problem on RC12 with SL6000 in either portrait or landscape modes, so it must be model-specific...
-
I have the same problem!
C3100 , pdaxrom beta2
-
I found a possible fix. Edit /usr/share/applications/xpdf.desktop and change the Exec line to something like this:
Exec=xpdf -geometry 640x420-0+0 -z 'width' /mnt/ide3/documents/media/reference/Ferry_English.pdf
Explanation:
-geometry 640x420-0+0 is standard option understand by (most/all?) X programs, this sets size and location of window
-z 'width' this is xpdf specific and sets zoom to page width
/mnt/ide3/documents/media/reference/Ferry_English.pdf opens this document, the purpose of this is to actually set xpdf's working directory to where most of my PDFs are stored. I tried using a Path entry in xpdf.desktop but that doesn't seem to have any effect, hence this kludge.
A similar technique could be used for other programs which are clueless about the window size/location was used the last time you ran them. For example, with gnumeric you would use: --geometry 640x420-0+0, note the double hyphen as opposed to xpdf which requires single hyphen. Use <program> --help on the command line to see what options a particular accepts.
Here's my observations on how this bug manifests itself:
When xpdf starts up the initial size of the window depends on the document opened.
- If the size of the window is wider/taller than the screen and you then maximise the window (which in this case makes it smaller), xpdf will still think it has the original window size to work on and hence scale the drawing accordingly. Thus when you view it on your smaller window parts of it is cutoff
- If the size of the window is narrower/shorter than the screen and you then maximise the window (which in this case makes it bigger), xpdf will still think it has the original window size to work on and hence scale the drawing accordingly. Thus when you view it on your larger window parts of it grey - xpdf will not use those parts and they will not get refreshed.
So by making xpdf startup with the specific window size that you want to use these scaling problems can be avoided.
-- cheers
-
Cool. Thanks for posting this info Desertrat.
How do you find viewing PDF's in your newly compiled DjVuLibre compared to Xpdf?
-
Cool. Thanks for posting this info Desertrat.
How do you find viewing PDF's in your newly compiled DjVuLibre compared to Xpdf?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122271\"][{POST_SNAPBACK}][/a][/div]
hmm, i will see if i can compile xpdf, then i could fix it and maybe add a file dialog to it too
-
Cool. Thanks for posting this info Desertrat.
How do you find viewing PDF's in your newly compiled DjVuLibre compared to Xpdf?
The program itself takes a little bit longer to startup than xpdf. But once up and running, viewing files and moving between pages is a lot snappier. Particularly when viewing pages laden with graphics as the Tux magazines (http://www.tuxmagazine.com/) often are. The djvu files are also a lot smaller than the pdf equivalent (eg one pdf I converted was originally about 20MB, as a djvu file it's 3.5MB, for graphics intensive docs the savings will not be so great - the 2 TUX mags that I converted gave about 50% reduction in size). The savings in space comes at a cost, the quality is not as good as the pdf original. This is only apparent when you zoom in several hundred percent, otherwise for regular viewing it is completely adequate (IMO at least).
hmm, i will see if i can compile xpdf, then i could fix it and maybe add a file dialog to it too
Um, maybe you could be more ambitious ( ) and do Evince instead? I had got as far as compiling the poppler library, then I got distracted and compiled DjVuLibre instead
-- cheers
-
Cool. Thanks for posting this info Desertrat.
How do you find viewing PDF's in your newly compiled DjVuLibre compared to Xpdf?
The program itself takes a little bit longer to startup than xpdf. But once up and running, viewing files and moving between pages is a lot snappier. Particularly when viewing pages laden with graphics as the Tux magazines (http://www.tuxmagazine.com/) often are. The djvu files are also a lot smaller than the pdf equivalent (eg one pdf I converted was originally about 20MB, as a djvu file it's 3.5MB, for graphics intensive docs the savings will not be so great - the 2 TUX mags that I converted gave about 50% reduction in size). The savings in space comes at a cost, the quality is not as good as the pdf original. This is only apparent when you zoom in several hundred percent, otherwise for regular viewing it is completely adequate (IMO at least).
hmm, i will see if i can compile xpdf, then i could fix it and maybe add a file dialog to it too
Um, maybe you could be more ambitious ( ) and do Evince instead? I had got as far as compiling the poppler library, then I got distracted and compiled DjVuLibre instead
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122308\"][{POST_SNAPBACK}][/a][/div]
here's my hacked version.
i discovered, you can just press o for a file dialog
-
Um, maybe you could be more ambitious ( ) and do Evince instead? I had got as far as compiling the poppler library, then I got distracted and compiled DjVuLibre instead
Evince has already been compiled but it's not on the contrib web site.
Here is the link
https://www.oesf.org/forums/index.php?showt...hl=evince&st=30 (https://www.oesf.org/forums/index.php?showtopic=9343&hl=evince&st=30)
-
Evince has already been compiled but it's not on the contrib web site.
Here is the link
https://www.oesf.org/forums/index.php?showt...hl=evince&st=30 (https://www.oesf.org/forums/index.php?showtopic=9343&hl=evince&st=30)
Thanks.
-
here's my hacked version.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122328\"][{POST_SNAPBACK}][/a][/div]
Thanks for posting this Meanie. What version is it?
-
here's my hacked version.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122328\"][{POST_SNAPBACK}][/a][/div]
Thanks for posting this Meanie. What version is it?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122452\"][{POST_SNAPBACK}][/a][/div]
3.01-1
Should be the same version as the one in the beta1 feed, so just replace the xpdf binary once you install that package.