ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt, Framemaker, and InDesign
Date: Mon, 30 Jun 2008 23:58:50 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.00.0806302344130.8783@nqv-yncgbc> (raw)
In-Reply-To: <op.udle2plinx1yh1@your-b27fb1c401>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1848 bytes --]

On Mon, 30 Jun 2008, Idris Samawi Hamid wrote:

> Hi Martin,
>
> On Mon, 30 Jun 2008 16:18:37 -0600, Martin Schröder <martin@oneiros.de>
> wrote:
>
>> 2008/6/30 Idris Samawi Hamid <ishamid@colostate.edu>:
>>> What does ConTeXt have that Framemaker does not?
>>
>> I don't know about ConTeXt, but I know that something like LaTeX's
>> \include/\includeonly was a new feature of Frame 7 (from 2002).
>
> What is \include/\includeonly?
>

Suppose you are writing a book with 15 chapters, and it takes a long time 
to compile your chapters. In LaTeX, you can include each chapter using 
\include {name of file} and then add a command \includeonly{a few 
chapters} on the top of your file. Only the chapters specified by 
\includeonly are included. So, it saves a lot of time in compiling the 
file. (I think there is also a command to exclude specific chapters).

It is roughly similar to compiling only a component of a big project in 
ConTeXt. However, I feel that the latex version works better since it 
maintains the numbering of chapters, etc.

For example, in latex if I include chapter 3 of a big book, its chapter 
number will be 3, and all the cross references to material outside that 
chapter will be correct.

In Context, if I compile the component containing chapter 3, its number 
will start from 1. I can get correct cross references by using 
\usereferences (and ignore the duplicate references warning), but the 
numbering of the compiled component is incorrect. This is one are where I 
wish context had better support.

Note that latex's method is not perfect. \include starts a new page, but 
that way it can ensure that the materical of included file is somewhat 
isolated with rest of the material. Context's \component does not start a 
new page, which is often times useful.

Aditya

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2008-07-01  3:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 16:53 Idris Samawi Hamid
2008-06-30 22:00 ` Charles P. Schaum
2008-06-30 22:18 ` Martin Schröder
2008-07-01  3:09   ` Idris Samawi Hamid
2008-07-01  3:58     ` Aditya Mahajan [this message]
2008-07-01  7:56       ` Hans Hagen
2008-07-01 13:25         ` Idris Samawi Hamid
2008-07-01 23:18         ` Aditya Mahajan
2008-07-02  6:29           ` Wolfgang Schuster

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=alpine.DEB.1.00.0806302344130.8783@nqv-yncgbc \
    --to=adityam@umich.edu \
    --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).