From: "Idris Samawi Hamid" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: default engine for texexec
Date: Sun, 30 Dec 2007 11:17:47 -0700 [thread overview]
Message-ID: <op.t35ufxoznx1yh1@your-b27fb1c401> (raw)
In-Reply-To: <20071230082946.GA12828@gaston.couberia.bzh>
Hi Peter,
On Sun, 30 Dec 2007 01:29:46 -0700, Peter Münster <pmlists@free.fr> wrote:
> with the command "texexec file", I want luatex to be used. And with the
> command "texexec --pdftex file" I want pdftex to be used.
IIRC there used to be an ini file with those options, but it's gone now.
For one thing, older engines like tex and omega are no longer supported
(no etex), luatex is still experimental, and aleph is obsolete (except for
testing for relevant luatex bugs). So pdftex is the only really solid
engine (I don't know anything about xetex).
So maybe Hans is waiting till mkiv stabilizes before giving us that option
back?
Best
Idris
--
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-30 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 22:22 Peter Münster
2007-12-29 23:04 ` Idris Samawi Hamid
2007-12-30 8:29 ` Peter Münster
2007-12-30 18:17 ` Idris Samawi Hamid [this message]
2007-12-30 21:16 ` Hans Hagen
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=op.t35ufxoznx1yh1@your-b27fb1c401 \
--to=ishamid@colostate.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).