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: Fri, 22 Mar 2013 08:31:23 +0100	[thread overview]
Message-ID: <710C7AA9-2A41-4793-841A-CC0757540CDC@web.de> (raw)
In-Reply-To: <20130321152603.13688b88@aga-netbook>

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:
	1) how the command and its parameters are portrayed
	2) full description of defaults values and their effects and side effects
	3) general intention of the command its parameters
	4) MWEs describing the standard use of all parameters
	5) MWEs for non standard use (Advanced technics)
	6) standrad way for referencing other commands

If everybody follows the conventions we can then combine all the parts to a 
comprehensive manuals. They will work as a reference and tutorial. 

When something new is introduced the group is informed and can update their
subject(s). 

I would be willing to help. Any other takers?

regards
	Keith.


 
Am 21.03.2013 um 15:26 schrieb Marcin Borkowski <mbork@wmi.amu.edu.pl>:

> Dnia 2013-03-21, o godz. 11:32:01
> Alan BRASLAU <alan.braslau@cea.fr> napisał(a):
> 
>> On Thu, 21 Mar 2013 11:19:24 +0100
>> Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote:
>> 
>>> Marcin wasn't talking about organizing the wiki page, but about
>>> writing up-to-date and complete manuals (in PDF) which is nearly
>>> impossible with the speed that Hans keeps developing ConTeXt ;).
>> 
>> Unless we find funding somewhere to assign someone sufficiently
>> competent to work full-time for Hans just to write and maintain
>> documentation.
>> 
>> This is not a bad idea if only we could get it sponsored...
> 
> I have an impression that I heard about something similar to GSoC, but
> for writing docs...
> 
> Also, it might not need a full-time job, even if you want to keep up
> with Hans' speed.  And even a good free book on, say, a "snapshot" of
> ConTeXt from some point in time (later than official manuals) would be
> useful.
> 

___________________________________________________________________________________
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:[~2013-03-22  7:31 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 [this message]
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=710C7AA9-2A41-4793-841A-CC0757540CDC@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).