From: plink <plink@veribox.net>
Subject: Re: Manual (English) Update soon?
Date: Fri, 29 Dec 2006 18:38:12 +0100 [thread overview]
Message-ID: <45955284.4040906@veribox.net> (raw)
In-Reply-To: <6faad9f00612281643w48c24d36t9997c7fdd943789a@mail.gmail.com>
Mojca Miklavec wrote:
> Well, the ConTeXt manual is one of the most stable components of
> ConTeXt indeed ;)
;-)
should be wikified ...
>> (IIRC, Hans is also a core team member of LuaTeX, so perhaps I should
>> just suck it up with LaTeX until LuaTeX is viable?)
>
> No reason for, as Aditya already mentioned.
Except if you need some more processing of the TeX contents, like some
people do :-(
In that case, since the mkiv stuff isn't available, currently you either
have to switch to "plain" luatex or to use ConTeXt with pdftex and maybe
weave another layer of ruby around the script onion that texexec had
become.
Both ways don't really come close to the zen of ConTeXt TeXnology, I
would assume.
next prev parent reply other threads:[~2006-12-29 17:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 21:10 Douglas Philips
2006-12-28 22:00 ` Aditya Mahajan
2006-12-29 16:14 ` Douglas Philips
2006-12-30 3:04 ` Mojca Miklavec
2006-12-30 9:28 ` Douglas Philips
2007-01-02 22:28 ` Henning Hraban Ramm
2006-12-30 5:47 ` Sanjoy Mahajan
2006-12-30 9:40 ` Douglas Philips
2006-12-30 11:43 ` Rolf Marvin Bøe Lindgren
2006-12-30 18:38 ` Sanjoy Mahajan
2006-12-30 19:45 ` Rolf Marvin Bøe Lindgren
2006-12-29 0:43 ` Mojca Miklavec
2006-12-29 1:58 ` John R. Culleton
2006-12-29 4:37 ` Idris Samawi Hamid
2006-12-29 16:35 ` Douglas Philips
2006-12-29 19:22 ` andrea valle
2006-12-30 9:20 ` Douglas Philips
2006-12-29 17:38 ` plink [this message]
2006-12-30 9:17 ` Douglas Philips
2007-01-01 22:32 ` 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=45955284.4040906@veribox.net \
--to=plink@veribox.net \
--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).