ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: seeking ConTeXt code
Date: Tue, 14 Sep 1999 01:29:03 +0200	[thread overview]
Message-ID: <37DD88BF.B967B5DF@wxs.nl> (raw)
In-Reply-To: <m3d7vmy2kh.fsf@kali.coe.uga.edu>

"Ed L. Cashin" wrote:

> I have been playing with this, and it seems to work, but it is has a
> much longer execution time compared to, e.g., psbook.

Indeed, but the difference is that here we are dealing with typesetting.
I'm thinking of adding features that act on the spread and so, in which
case psbook is less adequate. Another advantage of the tex method is
that is is pretty save on colors.  

> It seems that the "--pdfarrange" method is significantly faster.  Is
> that what you'd expect?

Sure, because here we only copy already typeset stuff. Both have their
pros and cons. 

> > Now, the main problem is that arrangement takes place in the last
> > stage.  This means running with the arrangement commented and then
> > run a last one with the arrangement. The reson behind this is that
> > otherwise all the references and indexes and lists get spoiled (page
> > 5 can be output before page 1).
> 
> I haven't been using documents that have references and lists in my
> experiments.  Are you saying that the --pdfarrange method will
> generate documents with incorrect indices, references, etc.?

No, but it will definitely loose all annotations. This no problem
because we're dealing with printed matter. In general, pdf inclusions
will loose annotations (there was a time distiller included them, which
could give nice effects: cropboxes migrating from illustrations to the
main document). 

This is one reason why we for instance wrote the flowchart module. That
way we could add hyperlinks in cells (and more) which isnearly
impossible with imported graphics. Expect more of this stuff in
context.  

> > When you use a5 on a4, you can use texexec. Just set up your document
> > for a5, and run texexec:
> >
> >   texexec --paper=a5a4 --print=up yourfile
> >
> > will run context untill all refs are sorted out, and then apply a last
> > pass doing the reshuffel.
> >
> > I can add a feature to texexec (--arrange) that does the 'commenting'
> > (sort of), so that one has full controll in the source. I'll give this
> > some thought.
> 
> What would be the advantage of the texexec --arrange option versus
> putting the pagination commands in the source?

It saves you commenting the arrangement out when doing normal runs,
although you could say: 

\startmode[arrange]

  all kind of setups 

\stopmode

... and for the final run: 

  texexec --mode=arrange --once 

etc etc. (It's not the easiest context things you've started with)

> I noticed that a while back Taco Hoekwater posted to the pdftex list a
> method that consisted of just directly noodling with the page number
> order in the PDF document itself.  You warned that the number of bytes
> has to stay the same, but it sounded like it would work.

Very dangerous, when 3 changes into 40 and 40 into 3 thereis a big
change that many objects have pointers one off. 

> That wouldn't work in this case, would it?  I'm putting the pages 2
> per sheet of paper.

Right. 

> > Concerning the manual, we will start uploading soon on a chapter by
> > chapter base. The first 4 chapters are in typesetting stage (chapter 4
> > is what you need).
> 
> Whoo!!  That is very good news!

(after eurotex ...) 

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------


  reply	other threads:[~1999-09-13 23:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-06  1:13 Ed L. Cashin
1999-09-06 19:26 ` Hans Hagen
1999-09-06 20:59   ` RH 6.0 teTeX (was Re: seeking ConTeXt code) (long) Ed L. Cashin
1999-09-07  7:54     ` Hans Hagen
1999-09-07 14:45       ` Ed L. Cashin
1999-09-08  3:08   ` seeking ConTeXt code Ed L. Cashin
1999-09-08  8:12     ` Hans Hagen
1999-09-09  0:01       ` Ed L. Cashin
1999-09-09  7:23         ` Hans Hagen
1999-09-13 20:33       ` Ed L. Cashin
1999-09-13 23:29         ` Hans Hagen [this message]
1999-09-08  8:35     ` Gilbert van den Dobbelsteen
1999-09-08 10:12       ` Hans Hagen
1999-09-09  8:37         ` Tobias Burnus
1999-09-08 12:11     ` Hans Hagen
1999-09-09  0:38       ` Ed L. Cashin
1999-09-09  7:13         ` Hans Hagen
1999-09-10 15:08           ` Ed L. Cashin
1999-09-10 16:13             ` Hans Hagen
1999-09-09  2:45   ` Ed L. Cashin
1999-09-09  7:04     ` Hans Hagen
1999-09-09  9:35   ` Hans Hagen
1999-09-09  9:37   ` Hans Hagen
1999-09-09 18:11     ` Berend de Boer
1999-09-09 10:05   ` Taco Hoekwater
1999-09-09 10:14   ` Taco Hoekwater
1999-09-09 10:26   ` Taco Hoekwater
1999-09-09 11:04   ` Taco Hoekwater

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=37DD88BF.B967B5DF@wxs.nl \
    --to=pragma@wxs.nl \
    --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).