From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: upto current
Date: Wed, 20 Mar 2013 18:54:17 +0100 [thread overview]
Message-ID: <3C82073C-9A1E-4DE2-AFB5-BDE3C0550994@web.de> (raw)
In-Reply-To: <20130320092558.1d0f33cd@aga-netbook>
Am 20.03.2013 um 09:25 schrieb Marcin Borkowski <mbork@wmi.amu.edu.pl>:
> Dnia 2013-03-20, o godz. 09:12:21
> "Keith J. Schultz" <keithjschultz@web.de> napisał(a):
>
>>
[snip, snip]
>> My suggestion would be to have garden have a manuals download
>> area where one can get the up to date manuals from Pragma and
>> where one can discern how old the others are. It should be also, easy
>> to find.
>>
>> regards
>> Keith.
>
> That is quite true, though not that easy. In essence, I think someone
> would have to be paid for tracking the mailing list and updating
> manuals. AFAIK, Sietse does a great job updating the wiki, but the
> wiki is not necessarily the easiest thing to go to for newbies (as you
> have noticed).
>
> It is quite obvious for me that Pragma won't fund such an enterprise
> (not that I'm claiming it should - of course not!). I think the only
> body which might do it is either TUG, either some other UG - but then, I
> guess they are already funding LaTeX3 (which is kind of a competitor -
> albeit friendly - to ConTeXt), either font projects (TeX Gyre!), which
> are quite beneficial to the ConTeXt ecosystem, too.
I do not get you here.
Garden just needs a little redesigning or more correctly cleaning up.
I see no need for funding.
I am not into wikis or I would offer to do it.
regards
Keith.
___________________________________________________________________________________
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-03-20 17:54 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
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 [this message]
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=3C82073C-9A1E-4DE2-AFB5-BDE3C0550994@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).