From: John Culleton <john@wexfordpress.com>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: structuring Context code using \input statements.
Date: Mon, 7 Feb 2011 16:39:30 -0500 [thread overview]
Message-ID: <201102071639.30315.john@wexfordpress.com> (raw)
In all forms of TeX it is my custom to start with a brief main file and
call the various components of the document into the input stream with
\input statements. The termination of the document is in the main file
with a \stoptext statement.
This works well with pdftex documents and also with
MKII documents. But it fails with MKIV documents. The Context program
will read and use an inserted program but will not return to the main
text stream in the file that did the inputting. It just displays an *
and hangs. Are there new rules in MKIV about breaking up a document
into separate files and inserting these in sequence via \input
statements?
--
John Culleton
Create Book Covers with Scribus:
http://www.booklocker.com/p/books/4055.html
Typesetting and indexing http://wexfordpress.com
book sales http://wexfordpress.net
Free barcode: http://www.tux.org/~milgram/bookland/
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2011-02-07 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 21:39 John Culleton [this message]
2011-02-07 22:55 ` Aditya Mahajan
2011-02-07 23:07 ` Hans Hagen
2011-02-08 14:35 ` John Culleton
2011-02-08 14:35 ` 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=201102071639.30315.john@wexfordpress.com \
--to=john@wexfordpress.com \
--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).