| 2009-04-30 15:20:41 |
Adam Buchbinder |
description |
Binary package hint: evince
If I encode an 850x1100 image with the "-dpi 100" option, it's written into the INFO block as reported by djvudump. If I then encode a 425x550 image with the "-dpi 50" option, it should, when viewed in Evince, show up at the same size--at 100% zoom, both should be the size of a standard letter sheet. However, in this case, the latter image shows up as half the size of the former. This makes, for instance, 72dpi scans difficult to view at the standard zoom levels, because they're didiculously tiny, and it makes 300dpi scans huge and slow to open.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: evince 2.24.1-0ubuntu1
ProcEnviron:
SHELL=/bin/bash
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SourcePackage: evince
Uname: Linux 2.6.27-11-generic i686 |
Binary package hint: evince
If I encode an 850x1100 image with the "-dpi 100" option, it's written into the INFO block as reported by djvudump. If I then encode a 425x550 image with the "-dpi 50" option, it should, when viewed in Evince, show up at the same size--at 100% zoom, both should be the size of a standard letter sheet. However, in this case, the latter image shows up as half the size of the former. This makes, for instance, 72dpi scans difficult to view at the standard zoom levels, because they're ridiculously tiny, and it makes 300dpi scans huge and slow to open.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: evince 2.24.1-0ubuntu1
ProcEnviron:
SHELL=/bin/bash
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SourcePackage: evince
Uname: Linux 2.6.27-11-generic i686 |
|
