Your message dated Sat, 11 May 2013 12:21:17 +0200
with message-id <1368267677.10049.6.camel@shepard>
and subject line Re: Should use PDF-provided page numbers to work with Beamer
presentations
has caused the Debian Bug report #656285,
regarding Should use PDF-provided page numbers to work with Beamer presentations
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
656285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656285
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pdf-presenter-console
Version: 2.0-6
Severity: normal
I use pdf-presenter console to present presentations produced using
LaTeX Beamer. I also make extensive use of slides with incremental
reveals, \pause, and other such mechanisms. Thus, I have presentations
which have 36 slides, but 75 pages in the PDF. pdf-presenter-console
presents my progress as "N/75", rather than "N/36", which makes it very
difficult to gauge my actual progress. evince knows how to read the
page numbers provided in the PDF, so while it knows (and displays) how
many pages the PDF has, it also displays the PDF-provided page numbers.
Please consider doing the same.
(If you think people might depend on the existing behavior, perhaps
pdf-presenter-console could have an option to continue using the raw PDF page
numbers. However, I think using the PDF-provided page numbers would
make much more sense as the default.)
Thanks,
Josh Triplett
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pdf-presenter-console depends on:
ii libatk1.0-0 2.2.0-2
ii libc6 2.13-24
ii libcairo2 1.10.2-6.2
ii libfontconfig1 2.8.0-3
ii libfreetype6 2.4.8-1
ii libgdk-pixbuf2.0-0 2.24.0-2
ii libglib2.0-0 2.28.6-1
ii libgtk2.0-0 2.24.7-1
ii libpango1.0-0 1.29.4-2
ii libpoppler-glib6 0.16.7-2+b1
ii libpoppler13 0.16.7-2+b1
pdf-presenter-console recommends no packages.
pdf-presenter-console suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.1-1
Hi,
On Wed, 2012-01-18 at 11:44 +1100, Josh Triplett wrote:
> I use pdf-presenter console to present presentations produced using
> LaTeX Beamer. I also make extensive use of slides with incremental
> reveals, \pause, and other such mechanisms. Thus, I have presentations
> which have 36 slides, but 75 pages in the PDF. pdf-presenter-console
> presents my progress as "N/75", rather than "N/36", which makes it very
> difficult to gauge my actual progress. evince knows how to read the
> page numbers provided in the PDF, so while it knows (and displays) how
> many pages the PDF has, it also displays the PDF-provided page numbers.
> Please consider doing the same.
I recently gave a Beamer-based presentation which used overlays (a.k.a.
\pause). For me, pdfpc correctly displayed the "logical" slide numbers
instead of the confusing "physical" page numbers.
I've just confirmed that pdfpc does indeed do "the right thing" (tm)
using the official demo presentation available from pdfpc's website:
https://github.com/downloads/davvil/pdfpc/pdfpc-demo.pdf
I'm therefore closing this bug now, please feel free to reopen if this
isn't actually fixed for you!
Best regards
Alexander Kurtz
signature.asc
Description: This is a digitally signed message part
--- End Message ---
