From: Hans Hagen <pragma@wxs.nl>
Subject: Re: The speed of development?
Date: Wed, 14 Dec 2005 23:21:51 +0100 [thread overview]
Message-ID: <43A09AFF.9060104@wxs.nl> (raw)
In-Reply-To: <86wti7l5ro.fsf@gmail.com>
leon wrote:
>Hi guys,
>
>I'm starting to use conTeXt. And thanks for all those people encourage
>me in my last email.
>
>I read in various places that the pace of development is fast. I don't
>get a clue of what that means. As far as I know LaTeX hasn't been
>updated for over 3 years. So how fast is conTeXt being developed? The
>conTeXt manual dated 2001 since pretty old to me. Am I right?
>
>
sure, but it's only one of the many manuals ... more detailed manuals
came later; see website for more details
(the texbook is older -)
concerning development ... it's driven by what we need here, by what
users demand, and what is fun to implement
Hans
next prev parent reply other threads:[~2005-12-14 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 21:37 leon
2005-12-14 22:21 ` Hans Hagen [this message]
2005-12-14 23:21 ` leon
2005-12-15 21:08 ` Mojca Miklavec
2005-12-15 21:43 ` leon
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=43A09AFF.9060104@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).