From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt on the Mac (TexShop). Problem of a newbie
Date: Thu, 10 Jan 2013 11:47:02 +0100 [thread overview]
Message-ID: <80E30FC8-C932-46B1-B03C-4F1319FB21B9@web.de> (raw)
In-Reply-To: <50EE85DA.6070207@wxs.nl>
Hi Hans,
I am kind of confused about the relationship between luatex and ConTeXt.
The way I read the wikis and web sites luatex and ConTeXt are basically two
different animals. They have a common core, but two different code bases, where
the ConTeXt group doing most the work advancing the Lua code base and those
changes integrated into the LuaTeX side.
Your statements below would suggest things are the other way around!?
Would your care to elaborate or anybody else for that matter if this request is not
to OT.
Thanx in advance.
regards
Keith.
Am 10.01.2013 um 10:11 schrieb Hans Hagen <pragma@wxs.nl>:
> [snip, snip]
> some of the presentation styles started out a experiments and therefore can have code that should be adapted if experiments have turned feature
>
> anyhow, the transition from mkii to mkiv involves rewrites and therefore there can be issues but normally they're fixed rather fast; also, updating is easy (just run first-setup again); it's the price we pay for using luatex, which is evolving
>
___________________________________________________________________________________
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:[~2013-01-10 10:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 15:07 Meigen, Thomas
2013-01-09 9:00 ` Hans Hagen
2013-01-09 16:01 ` Sietse Brouwer
2013-01-10 8:13 ` Meigen, Thomas
2013-01-10 9:11 ` Hans Hagen
2013-01-10 10:47 ` Keith J. Schultz [this message]
2013-01-10 11:19 ` Martin Schröder
2013-01-10 11:58 ` Hans Hagen
2013-01-10 12:01 ` Hans Hagen
2013-01-10 11:22 ` Aditya Mahajan
2013-01-10 13:03 ` Aditya Mahajan
2013-01-10 9:22 ` Keith J. Schultz
2013-01-11 10:58 ` Meigen, Thomas
2013-01-11 13:11 ` Hans Hagen
2013-01-11 11:32 ` Meigen, Thomas
2013-01-11 12:09 ` Khaled Hosny
2013-01-11 13:15 ` Hans Hagen
2013-01-11 23:13 ` Sietse Brouwer
[not found] ` <8A5FF695-AC2A-493E-81D6-322090E1B895@klinik.uni-wuerzburg.de>
2013-01-13 22:03 ` Meigen, Thomas
2013-01-13 22:44 ` Hans Hagen
[not found] <mailman.269.1357821208.2489.ntg-context@ntg.nl>
2013-01-10 14:17 ` Pavneet Arora
2013-01-10 14:23 ` Pavneet Arora
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=80E30FC8-C932-46B1-B03C-4F1319FB21B9@web.de \
--to=keithjschultz@web.de \
--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).