ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pavneet Arora <pavneet_arora@waroc.com>
To: ntg-context@ntg.nl
Subject: Re: ConTeXt on the Mac (TexShop). Problem of a newbie
Date: Thu, 10 Jan 2013 09:23:58 -0500	[thread overview]
Message-ID: <50EECEFE.6030807@waroc.com> (raw)
In-Reply-To: <mailman.269.1357821208.2489.ntg-context@ntg.nl>

Hans,

This is a most lucid explanation.  I have been waiting for this myself.

To quote the great American philosopher, Corporal Radar O'Reilly, from the 
television show of the 1970s, M*A*S*H:

Ah, Bark! [He was instructed to say Ah, Baaacccch! by Hawkeye Pierce]

I apologise in advance for this most peculiar and culturally specific bit of 
history.

Regards.


> ------------------------------
>
> Message: 5
> Date: Thu, 10 Jan 2013 12:58:43 +0100
> From: Hans Hagen <pragma@wxs.nl>
> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Subject: Re: [NTG-context] ConTeXt on the Mac (TexShop). Problem of a
> 	newbie
> Message-ID: <50EEACF3.9040602@wxs.nl>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 1/10/2013 12:19 PM, Martin Schr?der wrote:
>> 2013/1/10 Keith J. Schultz <keithjschultz@web.de>:
>>> I am kind of confused about the relationship between luatex and ConTeXt.
>>
>> http://www.tug.org/levels.html
>>
>> ConTeXt MkIV needs LuaTeX.
>
> That's a somewhat confusing description.
>
> (1) Context is just a format, so it should be mentioned as format.
>
> (2) We call all instances context, i.e. we don't combine engine names
> with 'context' so there is no 'pdfcontext', although one could do that.
>
> (3) As there are language dependent user interfaces, we have more
> formats (cont-en, cont-nl, ...).
>
> (4) We use a management script to run the engine with the context
> format. Reasons for this are: we need to manage multiple runs, we might
> need to call intermediate programs (in mkii for instance we need to sort
> indices).
>
> (5) This also permits us to present to user with an engine independent
> call to context. In mkii we had 'texexec' (on top of a more generic
> script manager called texmfstart), in mkiv we have 'context' (and again
> a script manager called mtxrun).
>
> Now, to come to luatex: this project is quite related to context as it
> all started in the context community. We also use context for testing
> and exploring new functionality. For this we use mkiv/mkvi which is a
> rewrite of context using the full potential of luatex so that we can go
> beyond what traditional tex engines can do. We explicitly have chosen
> for a lua + tex combination so that we don't have to hardcode solutions
> in the engine (macro packages have too many conflicting demands anyway)
> and are more future proof.
>
> Given that mkii is frozen, and given that type1 fonts are sort of
> obsolete (context has always been an early adopter of lm and gyre
> fonts), and given that utf is the way to go (so no messing with input
> and font encodings any more), and given some more reasons, in practice
> users will no longer use pdftex and/or xetex but luatex. In that sense
> context depends on luatex and also keep the development of that engine
> going.
>
> The philosophy of context is that by having most functionality in the
> core, users can rather easy create their own styles (the average style
> has not that many lines anyway). I'm always sort of puzzled when I see
> remarks that context is close to plain, as I cannot see where that
> conclusion comes from. The whole reason that context exists is that I
> didn't want to hack around in low level style files and deal with funny
> commands having @ in their names.
>
> Hans
>
> -----------------------------------------------------------------
>                                             Hans Hagen | PRAGMA ADE
>                 Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>       tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
>                                                | www.pragma-pod.nl
> -----------------------------------------------------------------



-- 
-----
- Pavneet Arora

Waroc Fine Audio + Custom Home Cinema
www.waroc.com  416.937.WAROC (9276)

___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2013-01-10 14:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.269.1357821208.2489.ntg-context@ntg.nl>
2013-01-10 14:17 ` Pavneet Arora
2013-01-10 14:23 ` Pavneet Arora [this message]
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
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

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=50EECEFE.6030807@waroc.com \
    --to=pavneet_arora@waroc.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).