ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt, XeTeX, ect was Re: OpenType in Windows
Date: Thu, 05 Apr 2007 14:23:34 +0100	[thread overview]
Message-ID: <E1HZRw6-0005nD-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Thu, 05 Apr 2007 13:14:59 +0200." <6BF610EA-E849-4E3D-945F-F39B8A20EC79@di.unito.it>

> What does this exactly mean (from wikipedia)?
> "XeTeX works well with both LaTeX and ConTeXt."

XeTeX, PDFTeX, eTeX, and TeX (Knuth's original TeX) are conceptually
at the same level.  The ConTeXt documents (and kpathsea) call this
level the engine.  They all understand basically the same macro
language, the one Knuth described in the _TeXBook_.  

But they have slight differences.  For example, TeX produces DVI
output.  eTeX does too but it adds a few more commands ('primitives')
to the macro language.  PDFTeX produces PDF directly (or can produce
DVI) and has, relative to regular TeX, new macro commands to support
features of PDF; for example, \pdfpagewidth is new to PDFTeX.  Regular
TeX doesn't have an equivalent because the DVI format does not include
a notion of page size.  PDFTeX, from v1.40, also incorporates those
eTeX commands.  And XeTeX has commands to support OpenType, which is
the new standard font format.

LaTeX and ConTeXt are large programs ('macro packages') written on top
of the engine.  Namely, the program -- whether LaTeX or ConTeXt -- is
written in the macro language of the engine.  Most of the program is
independent of the engine, but there are a few changes needed; the
program usually detects which engine is being used underneath it and
adjusts what it does accordingly.

For LaTeX, you choose the engine by the name of the program you run:

* latex    -- uses regular TeX (actually, now it uses PDFTeX pretending
  to be regular TeX)
* pdflatex -- uses PDFTeX
* xelatex  -- uses XeTeX

For ConTeXt, you choose the engine by the '--engine' option to
texexec.  For example: "texexec --engine=pdftex file.tex" will make
you file.pdf.  But as the manual entry now says, you usually do not
need to specify the engine:

       --engine=texengine 
              Specify the program to do the hard work of typesetting.
              Currently either pdftex (the default), xetex, or aleph.
              The luatex value is experimental.  The --engine option
              is not usually needed.  Instead, let texexec figure out
              the setting based on other command-line information.
              See for example the --xetex or --pdf switches.  

So 
* "texexec --xetex file.tex" : uses XeTeX
* "texexec --pdf file.tex"   : uses PDFTeX
* "texexec file.tex"         : also uses PDFTeX (the --pdf option is
                               now the default to texexec)

I hope this explanation clarifies.  If so, you can Wikify (on
wikipedia and/or the ConTeXt wiki)!

-Sanjoy

`Not all those who wander are lost.' (J.R.R. Tolkien)

  parent reply	other threads:[~2007-04-05 13:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1175680802.12474.ntg-context@ntg.nl>
2007-04-04 22:08 ` Vyatcheslav Yatskovsky
2007-04-05  0:06   ` George N. White III
2007-04-05 10:18   ` Mojca Miklavec
2007-04-05 11:14     ` ConTeXt, XeTeX, ect was " Andrea Valle
2007-04-05 12:49       ` George N. White III
2007-04-05 13:23       ` Sanjoy Mahajan [this message]
2007-04-05 13:59         ` luigi scarso
2007-04-05 15:12         ` Andrea Valle

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=E1HZRw6-0005nD-00@skye.ra.phy.cam.ac.uk \
    --to=sanjoy@mrao.cam.ac.uk \
    --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).