ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Christopher Creutzig <christopher@creutzig.de>
Subject: Re: t-rsteps and starttyping
Date: Fri, 23 Sep 2005 15:21:56 +0200	[thread overview]
Message-ID: <43340174.2070805@creutzig.de> (raw)
In-Reply-To: <4333DCF7.9@wxs.nl>

Hans Hagen wrote:
> also, when collecting and flushing pieces of content, spacing is a
> tricky business (watch closely to presentations made quick and you'll
> notice those side effects)

 That is why ppower4 is such a nice alternative:  It inserts just some
pdf comments and otherwise leaves the typesetting alone.  Then a
postprocessor takes the pdf file and creates a new one, with everything
left at its original position, but appearing only on the pages (a slide
is built up by jumping to the next page) where it is supposed to appear.

> the content, presentation and audience, which in practice means that i
> don't use general solutions (apart from the fact that i don't like

 Well, a general solution for the isolated requiement of “having
considered content, audience and everything, I want my text/gfx/
whatever appear step-wise“ would be a good thing, imho.  And I did in
the past also use things like removing the full stop when stepping from

   This implies A.

to

   This implies A and therefore, B.


 I have also seen a presentation where the speaker sketched a proof of
some lemma, then generelized it and simply exchanged the relevant words
in the lemma.  The new words were shorter, so there was some space to
the left and right of them and they had some contrast color.  The effect
was not just “cool” and “I don't think Powerpoint could do that” –
what's more important is that this was by far the clearest way of
getting the message across.


 Is there a way of having \installprogram for only for after the *last*
run?  (I don't think there could be a systemmode for the last run, but
texexec knows it has done the last run, so there might be some file.tui
line doing this kind of magic.)


Christopher

  reply	other threads:[~2005-09-23 13:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 16:41 Peter Münster
2005-06-25 11:08 ` Otared KAVIAN
2005-06-25 11:42   ` Peter Münster
2005-06-27 10:56   ` Hans Hagen
2005-06-28 18:16     ` Peter Münster
2005-06-27 22:06 ` David Munger
2005-09-12 17:04   ` Peter Münster
2005-09-12 21:57     ` David Munger
2005-09-21 12:38       ` Christopher Creutzig
2005-09-21 14:00         ` David Munger
2005-09-21 14:13           ` Taco Hoekwater
2005-09-21 22:16             ` David Munger
2005-09-22  6:56               ` Christopher Creutzig
2005-09-22 15:24                 ` David Munger
2005-09-22 16:56                   ` Hans Hagen
2005-09-22 20:02                     ` David Munger
2005-09-22 20:39                       ` Hans Hagen
2005-09-23  2:34                         ` David Munger
2005-09-23  7:11                           ` Mojca Miklavec
2005-09-23  8:51                         ` Peter Münster
2005-09-23 10:46                           ` Hans Hagen
2005-09-23 13:21                             ` Christopher Creutzig [this message]
2005-09-25 21:42                               ` Hans Hagen
2005-09-28 11:13                                 ` Christopher Creutzig
2005-09-26 15:04           ` footnote for author (\thanks) Albrecht Kauffmann
2005-09-26 16:08             ` Adam Lindsay
2005-09-26 15:34           ` footnote numbering Albrecht Kauffmann

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=43340174.2070805@creutzig.de \
    --to=christopher@creutzig.de \
    --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).