From: Hans Hagen <pragma@wxs.nl>
Subject: Re: A new manual
Date: Fri, 29 Sep 2006 22:09:32 +0200 [thread overview]
Message-ID: <451D7D7C.3050900@wxs.nl> (raw)
In-Reply-To: <22af238a0609290719l4ceed250m171555be4bf793e3@mail.gmail.com>
gnwiii@gmail.com wrote:
>
> I don't agree that lack of a current manual is a big problem for
> potential users of ConteXt. In my experience, the biggest problem is
> with the 3rd party tools (perl, ghostscript, ruby) on Win32 and legacy
> commercial unix (where ruby is not provided and the system perl will
> be a very old version).
>
actually, one could run context using "pdftex --fmt ...... " but it's
less convenient;
technically i could generate most of the tuo file directly (although
index sorting always has to rely on an external prog)
some two pass data (cross ref etc) can be loaded before an aux file is
written, but toc info cannot, and tex itself cannot rename a temp file
afterwards; because context can create tocs at any level any time, this
means that there will always be a need for an separate read and write
file (actuallym this is also true for more two pass data since some data
structures may be defined anywhere in teh document which also leads to
async loading)
in luatex, i will probably write the index sorter in lua as well as
support a different two pass info model as well which means that in
principle one could provide an embedded kind of texexec funtionality; of
course multiple runs still have to be managed by some external script
then but this can be simple since tex itself can signal the need for that
don't be surprised if contex mkiv provides a different user experience
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.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-09-29 20:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 13:20 John R. Culleton
2006-09-28 14:42 ` Nikolai Weibull
2006-09-28 16:42 ` Marcus Vinicius Mesquita de So
2006-09-28 18:54 ` Alexander Lazic
2006-09-29 7:09 ` Ricard Roca
2006-09-29 14:19 ` gnwiii
2006-09-29 17:00 ` John R. Culleton
2006-10-29 12:57 ` Geoffrey Alan Washburn
2006-11-01 17:52 ` Printing ConTeXt books on Lulu? (Was: A new manual) Geoffrey Alan Washburn
2006-11-01 18:19 ` Matthias Weber
2006-11-01 19:07 ` Geoffrey Alan Washburn
2006-09-29 20:09 ` Hans Hagen [this message]
2006-10-04 23:21 ` A new manual Aditya Mahajan
2006-10-05 6:51 ` Taco Hoekwater
2006-10-02 17:09 ` fdu.xiaojf
2006-09-29 7:57 A new Manual Fidel Viegas
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=451D7D7C.3050900@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).