From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [texhax] Choosing TeX um ... stuff
Date: Thu, 18 Nov 2010 09:35:46 +0100 [thread overview]
Message-ID: <AANLkTim5JxuVMKnb6axOuKK5SNikny-cpt_43+_0Xi6n@mail.gmail.com> (raw)
In-Reply-To: <1290031564.4ce451cc54c84@imp.free.fr>
On Wed, Nov 17, 2010 at 11:06 PM, Paul Isambert <zappathustra@free.fr> wrote:
> Selon "Philip Taylor (Webmaster, Ret'd)" <P.Taylor@rhul.ac.uk>:
>
>>
>>
>> Peter Davis wrote:
>> > 2. True or False: plain TeX and LaTeX(2e) are warhorses ... been
>> > around for decades, quirks well known, lots of documentation, etc.
>>
>> Yes, except that while Plain TeX has more-or-less remained
>> static (modulo essential bug fixes by Don), LaTeX2e has
>> continued to evolve. I have heard rumours that this particular
>> evolutionary branch may have come to an end, but I have
>> no definite knowledge of this.
>
> And plain TeX doesn't have a lot of documentation. Anyway there isn't much to
> document. Basically using plain TeX means you need a very good knowledge of the
> engine, and you'll write tons of macros (in a way there are no plain TeX users,
> only users of personal formats based on plain).
I consider eplain as something "useful" between plain and latex
We should also consider that, in general,
0<size(plain)<size(eplain)<size(latex)<size(context_mkii)
and
speed(context_mkii)<=speed(latex)<speed(eplain)<speed(plain)
So for "trivial" typographic problems as automatic typesetting of labels
maybe eplain can be the right choice -- it's fast and doesn't consume
much memory hence you can have many instances.
ConTeXt mkiv is something new: while it's still "TeX", it has so many
"practical"
news that it needs time to understand all implications.
Also the engine (luatex) is still unfinished (currently at 64%) and
mkiv evolves as luatex evelves --- i.e. it's still "unstable" of one
compares with mkii.
--
luigi
___________________________________________________________________________________
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 prev parent reply other threads:[~2010-11-18 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 21:23 Peter Davis
2010-11-17 21:38 ` Mojca Miklavec
2010-11-17 21:51 ` Philip Taylor (Webmaster, Ret'd)
2010-11-17 22:06 ` Paul Isambert
2010-11-18 8:24 ` [texhax] " Hans Hagen
2010-11-18 8:35 ` luigi scarso [this message]
2010-11-18 10:56 ` Philip Taylor (Webmaster, Ret'd)
2010-11-17 22:00 ` Hans Hagen
2010-11-18 1:29 ` Peter Davis
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=AANLkTim5JxuVMKnb6axOuKK5SNikny-cpt_43+_0Xi6n@mail.gmail.com \
--to=luigi.scarso@gmail.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).