ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: upto current
Date: Mon, 25 Mar 2013 09:02:39 +0100	[thread overview]
Message-ID: <3F06978B-6930-45F0-BFB5-71E27AD0B786@web.de> (raw)
In-Reply-To: <514C685A.1000609@meahan.net>

Hi Bill,

Am 22.03.2013 um 15:19 schrieb Bill Meahan <subscribed_lists@meahan.net>:

> On 03/22/2013 03:31 AM, Keith J. Schultz wrote:
>> Hi All,
>> 
>> Maybe, we could setup a collaborative work group to do the documentation.
>> 
>> That is a group of us are responsible for certain groups of commands. This way
>> the manuals can become more complete. That way some of the more advance
>> stuff that is hardly documented finally gets documented.
>> 
>> What we would need is a specification for:
>>   [snip]
> In 45+ years of programming[1] it has never ceased to amaze me how the wheel has to be reinvented for every new system whether language, macro package or whatever. Why do it again? Why not adopt some documentation system that is already widely-used and for which infrastructure and knowledge of use is already in place?

	I agree with your statement fully. Specification is a loaded word, too!
	What I was trying to say that we need convention how things are to be laid out!
	Setting up, maybe, a module to facilitate a common look. Otherwise the manuals
	will be a mess of styles and clarity. 
 
> I have no investment in any particular system. I'm happily generating other types of non-computer-related documents using reStructuredText since I can easily convert that various publication formats as required without separate source files for each format. It seems to me docutils has everything that would be needed to document ConTeXt and is very widely used given the popularity of Python (which makes me cringe). If doxygen or something else would work better, so be it. The point is, **use something that exists instead of expending time and effort reinventing the wheel yet again!**
	I was thinking of using ConTeXt!
> 
> [1] I was, am and will be a "programmer" and not a "software developer" or "software engineer." The term adequately depicts what I did/do while the others are simply too pretentious. Find the old article "Real Programmers Don't Use Pascal" in an archive somewhere -- I've been a "real programmer" and I suspect Hans is, too. :)
> 
> Sorry for the rants but it is so frustrating to have to install so many different language support and documentation systems simply because I use FOSS tools exclusively.
	No Problem.

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
___________________________________________________________________________________


  parent reply	other threads:[~2013-03-25  8:02 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
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 [this message]
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=3F06978B-6930-45F0-BFB5-71E27AD0B786@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).