Bug#325732: O: pdfscreen -- Make PDF documents which are printable and readable on screen too
Package: wnpp
Severity: normal
The current maintainer of pdfscreen, Viral Shah <viral@debian.org>,
is apparently not active anymore. Therefore, I orphan this package
now. If you want to be the new maintainer, please take it -- see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.
Some information about this package:
Package: pdfscreen
Binary: pdfscreen
Version: 1.5-6
Priority: optional
Section: tex
Maintainer: Debian QA Group <packages@qa.debian.org>
Build-Depends-Indep: debhelper (>> 3.0.0)
Architecture: all
Standards-Version: 3.5.2
Format: 1.0
Directory: pool/main/p/pdfscreen
Files:
271195beec1a250bc573905fb5833b7a 576 pdfscreen_1.5-6.dsc
580f6557b9d870689f5fccb24f85d14c 742926 pdfscreen_1.5.orig.tar.gz
45207efdac8c76fadc202a57f4213cff 9418 pdfscreen_1.5-6.diff.gz
Package: pdfscreen
Priority: optional
Section: tex
Installed-Size: 1072
Maintainer: Debian QA Group <packages@qa.debian.org>
Architecture: all
Version: 1.5-6
Depends: tetex-bin
Recommends: pdf-viewer, tetex-extra
Filename: pool/main/p/pdfscreen/pdfscreen_1.5-6_all.deb
Size: 770172
MD5sum: e4d21aa0586895c0c97af513be792de0
Description: Make PDF documents which are printable and readable on screen too
pdfscreen is an extension of the hyperref package to provide a
screen-based document design. This package helps to generate pdf
documents that are readable on screen and will fit the screen's aspect
ratio. Also it can be used with various options to produce regular
print versions of the same document without any extra effort.
.
One important utility of this package is to generate slides for
talks, seminars etc. It produces a pdf file which can be used for
a slideshow on any machine which has a pdf viewer. (Preferably acroread).
.
The homepage of this project is http://www.river-valley.com/download
Tag: interface::commandline, role::sw:utility, use::converting, works-with::text:pdf, works-with::text:tex
(This package seems to have been left out in the original bug filing;
cf. #192696, #192697, #192698, #192699.)
Reply to: