ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: upto current
Date: Wed, 20 Mar 2013 07:05:05 +0100	[thread overview]
Message-ID: <918676C5-3AD6-456C-B75D-3A4F130D1CBD@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.02.1303191434180.7751@ybpnyubfg.ybpnyqbznva>


On 19 mars 2013, at 19:47, Aditya Mahajan <adityam@umich.edu> wrote:

> […]Although most active users use ConTeXt standalone and are willing to update frequently, TL still plays an important role in introducing new users to ConTeXt. An experienced TeX user who wants to try ConTeXt is more likely to try ConTeXt distributed as part of TL rather than ConTeXt standalone. When there are serious bugs with ConTeXt TL, it gives the impression that ConTeXt is not a mature macro package.

Hi,

To support what suggests Aditya, I would like to say that the main issue with the current state of ConTeXt in TeXLive (either mkii or mkiv) is that most « lambda » users of TeX whom I know in the mathematics world and in accademia, that is:
	--- users who are not familiar with what should be changed in TeXLive, 
	--- users who don't even know TeX and LaTeX are not synonyms, 
	--- users who don't know that there exist another environments and macro packages for typesetting tex-files, 
	--- users who don't know that using ConTeXt one can do better typesetting, and that it has better features, 
all those users are not going to install a stand alone ConTeXt. They would use TeXLive, they would try everything in it, but all they want is to write a paper and typeset it with a TeX package with a single command (or in the case of Mac users, from within TeXShop or another editor). Most of them do not even know where TeXLive sits on their computer, and they don't know how to install something new.
Unfortunately, the ConTeXt in TeXLive does not work out of the box: the user has to issue a few commands before he can typeset a file with ConTeXt, either mkii or mkiv (for instance on my installation of TeXLive, after having issued a few commands, which I don't remember right now, I can use ConTeXt with LuaTeX, that is mkiv, but I cannot use mkii).

For my part I have been advocating ConTeXt among my colleagues (especially for course materials and books, since submitting a paper to a journal is essentially impossible if it is a ConTeXt file). Most of them agree that ConTeXt gives a much better result, but when it comes to how to use ConTeXt from TeXLive they are afraid and don't go further. For some of them I have installed a stand alone ConTeXt, but most of them do not update their installation, since they would not use the most recent features or improvements (for most of day to day typesettings, when one does not use complexe features, even a beta version is sufficiently stable for such users).

So my pledge is this: make any stable version of ConTeXt in TeXLive so that it works and typesets a tex-file « out of the box », without needing to issue any command other than:
	context myfile.tex
This is the case with LaTeX inside TeXLive, and so I cannot see any strong reason for ConTeXt not having the same behavior.

Best regards: OKs
___________________________________________________________________________________
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-03-20  6:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 18:16 Hans Hagen
2013-03-19 18:47 ` Aditya Mahajan
2013-03-19 19:05   ` Hans Hagen
2013-03-20  1:52     ` Aditya Mahajan
2013-03-20  6:05   ` Otared Kavian [this message]
2013-03-20  8:05     ` Meer H. van der
2013-03-20  8:19     ` Keith J. Schultz
2013-03-20  8:40     ` Hans Hagen
2013-03-20  9:27       ` Mojca Miklavec
2013-03-20  9:37         ` Hans Hagen
2013-03-20  8:12 ` Keith J. Schultz
2013-03-20  8:25   ` Marcin Borkowski
2013-03-20 17:54     ` Keith J. Schultz
2013-03-21 10:19       ` Mojca Miklavec
2013-03-21 10:32         ` Alan BRASLAU
2013-03-21 14:26           ` Marcin Borkowski
2013-03-22  7:31             ` Keith J. Schultz
2013-03-22  8:26               ` command reference (was: upto current) Peter Münster
2013-03-22 10:11                 ` Procházka Lukáš Ing. - Pontex s. r. o.
2013-03-22 10:25                   ` command reference Peter Münster
2013-03-22 12:04                   ` Hans Hagen
2013-03-22 14:42                   ` command reference (was: upto current) Sietse Brouwer
2013-03-22 16:07                     ` Sietse Brouwer
2013-03-22 17:21                       ` command reference Hans Hagen
2013-03-24 21:48                         ` Sietse Brouwer
2013-03-25  9:42                       ` command reference (was: upto current) Keith J. Schultz
2013-03-25  9:34                 ` Keith J. Schultz
2013-03-22 14:19               ` upto current Bill Meahan
2013-03-22 14:32                 ` Taco Hoekwater
2013-03-22 14:37                   ` luigi scarso
2013-03-22 14:47                 ` Hans Hagen
2013-03-25  8:02                 ` Keith J. Schultz
2013-03-20  8:49   ` 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=918676C5-3AD6-456C-B75D-3A4F130D1CBD@gmail.com \
    --to=otared@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).