From: Maurice Diamantini <Maurice.Diamantini@ensta.fr>
Cc: Maurice Diamantini <Maurice.Diamantini@ensta.fr>
Subject: Re: \presentationstep in standard pdf format
Date: Wed, 3 Nov 2004 08:47:05 +0100 [thread overview]
Message-ID: <8E46A248-2D6C-11D9-B3C8-000A9595B57C@ensta.fr> (raw)
In-Reply-To: <1099434120.15629.10.camel@m51.ASTRO.UMontreal.CA>
Le 2 nov. 04, à 23:22, David Munger a écrit :
> Nothing seems to work here. I'm afraid the problem is indeed that
> Acrobat Reader under Linux is not really JavaScript aware...
>
> Would it be possible to implement the steps commands such that steps
> span over multiple slides instead of being managed by JavaScript?
>
> David
I aggree with David that having the ConTeXt presentation feature
without needed javascript would realy be great.
Pdf is a standard, but not javascript.
It's realy nice to come to a seminar only with a pdf file without
worrying about which pdf reader tool exists on the host computer.
- Even with acroread 6.02 on osx there is some problem with some button
(I don't remember which problem, but I just remember it's not
reliable);
- Also Preview, the fastest pdf reader on osx (provide by Apple, then
the it is standard pdf reader on osx) don't support javascript;
- linux doesn't have pdf+javascript reader.
So I think that ConTeXt should provide a mean (option in textexec)
to make pdf-only version of presentation.
Finaly there could be three output levels for pdf presentation :
1 - presentation step using javascript (with allow blinking, merging,
zooming or other nice flashing features ;-)
2 - presentation step without javascript (one pdf page by step)
=> Good format for presentation by foreign pdf reader
3 - pdf file one pdf page for each final step by page
=> Good format for printing 2up or 4up slides
This third output would also allow to print a "slide + comment"
version of the presentation for the speacker.
The option of texexec could be something like
--pdfonly
instead of --pdf, or simply
--use-javascript=false
Maurice,
next prev parent reply other threads:[~2004-11-03 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 6:04 \presentationstep David Munger
2004-11-02 7:45 ` \presentationstep Henning Hraban Ramm
2004-11-02 9:58 ` \presentationstep Hans Hagen
2004-11-02 22:22 ` \presentationstep David Munger
2004-11-02 22:55 ` \presentationstep h h extern
2004-11-02 23:38 ` \presentationstep David Munger
2004-11-03 9:39 ` \presentationstep Hans Hagen
2004-11-03 7:47 ` Maurice Diamantini [this message]
2004-11-09 10:18 ` \presentationstep Eckhart Guthöhrlein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8E46A248-2D6C-11D9-B3C8-000A9595B57C@ensta.fr \
--to=maurice.diamantini@ensta.fr \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).