ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: State of documentation of ConTeXt?
Date: Wed, 16 Jul 2014 00:54:27 +0200	[thread overview]
Message-ID: <53C5B123.7060509@wxs.nl> (raw)
In-Reply-To: <D26ED339-C89F-4C46-BDA9-11CA956715EB@trichotomic.net>

On 7/16/2014 12:26 AM, David Wooten wrote:
> On Jul 15, 2014, at 2:59 AM, Gerben Wierda <Gerben.Wierda@rna.nl
> <mailto:Gerben.Wierda@rna.nl>> wrote:
>
>> I like ConTeXt (still do, I liked its approach when I first
>> encountered it). But the project is more the ongoing private tinkering
>> of a small in-crowd (that communicates with some followers).
>>
>> ConTeXt is managed a bit like a small group of researchers sharing a
>> couple of complex and undocumented models/programs and tinkering with
>> them as they go along. It’s an activity without formal design, but
>> with a lot of trial-and-error/testing.
>>
>> Given that status (and the fact that it has had that status for over a
>> /decennium/), I don’t expect it to ever become a serious product that
>> is (semi-)professionally managed. I prefer content over management
>> every day, but something like this needs some minimal management. That
>> requires both time (=money) and capabilities. Besides, the tinkering
>> researchers may not be inclined to do that, they want to tinker.
>
> Agreed, though for my part with the opposite emphasis. I do not think
> ConTeXt is meant to be a “serious product”, as in /being developed to be
> a product in the “marketplace” of  typesetting software — even open/free
> software. /My impression is exactly yours, it is being developed
> primarily for the purposes of Pragma—a small in-crowd no doubt—but with

don't get me wrong: the development is to a large extend possible 
because we can use it at pragma (it make sit possible to do things that 
often cannot be done otherwise) but most of the features that have been 
added the last years as well as numerous additional options are purely 
user driven: most styles we write are rather simple .. the complexity 
comes from the often messy or complex or to-be-manipulated content and 
range of products; so, it being mostly user driven (but within the 
constraints that we keep a relative stable core) also means that users 
have a responsibility for helping with documentation

> extraordinarily generous support for a small community of non-Pragma
> people interested in using it. I’m /grateful/ to have access to ConTeXt,
> as for me it’s the only sane method of typesetting the kind of documents
> I wish to typeset — /not /LaTeX, /not /InDesign, /not /Plain TeX, … I
> can tell you that every question or suggestion I’ve had has been
> responded to in the most generous form in this community, which I cannot
> say about /any other/ platform I’ve used, typesetting or otherwise.

keep in mind that context has been part of the tex distributions for 
quite a while now (nearly 20 years), that there are others than me who 
know the source code pretty well (which means that it doesn't depend on 
pragma), that the context crowd has been actively involved in 
development of (and even triggered) general tex developments (..., 
luatex, mplib, fonts, ...) so it's not as isolated as you suggest.

once the move from mkii to mkiv is finishes and luatex is kind of done, 
there might be time for writing more documentation; we're far from retiring

of the other macro packages, plain tex is frozen, and latex dev is quite 
controlled too (anyone can write additional code for any macro package)

(and the context mailing list is one of the more active tex related 
lists and not the smallest either)

> It’s suspect to take umbrage on another’s behalf, but “tinkering
> researchers may not be inclined to do that, they want to tinker” — It’s
> absurd to suggest that Hans &co. are “tinkering” for the sake of tinkering.

sometimes we do, when we explore new posibilities,

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


  reply	other threads:[~2014-07-15 22:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 12:18 Gerben Wierda
2014-07-14 13:03 ` Rob Heusdens
2014-07-14 17:29   ` Hans Hagen
2014-07-15  9:59     ` Gerben Wierda
2014-07-15 14:42       ` Mojca Miklavec
2014-07-16 11:24         ` Rob Heusdens
2014-07-16 12:14         ` Alan BRASLAU
2014-07-16 15:08           ` Russ Urquhart
2014-07-16 15:20             ` Hans Hagen
2014-07-16 15:23               ` luigi scarso
2014-07-17 16:28             ` Mica Semrick
2014-07-15 14:55       ` luigi scarso
2014-07-15 15:33         ` Yuri Teixeira
2014-07-15 20:08           ` Hans Hagen
2014-07-15 20:23       ` Hans Hagen
2014-07-15 22:26       ` David Wooten
2014-07-15 22:54         ` Hans Hagen [this message]
2014-07-15 23:10           ` David Wooten
2014-07-16  6:30           ` Gour
2014-07-20 12:14         ` Gerben Wierda
2014-07-20 14:55           ` Gerben Wierda
2014-07-20 20:24           ` Mojca Miklavec
2014-07-20 21:07             ` Gerben Wierda
2014-07-21  3:07               ` Henning Hraban Ramm
2014-07-23 12:36               ` Ulrike Fischer

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=53C5B123.7060509@wxs.nl \
    --to=pragma@wxs.nl \
    --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).