From: Uwe Koloska <ml@koloro.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: cont-enp.pdf on lulu
Date: Tue, 29 Jul 2008 01:07:43 +0200 [thread overview]
Message-ID: <200807290107.43947.ml@koloro.de> (raw)
In-Reply-To: <CB153721-6834-498F-BF4A-59FAB6AC0EAA@rna.nl>
Hello,
Am Montag, 28. Juli 2008 schrieb Gerben Wierda:
> I have an idea. Why not have a live ConTeXt manual.pdf where you add
> something in the proper location and compile the document every time
> you answer a question from a user? As you are the person answering
> anyway, it should be little extra work.
A good idea! But from my pov it should be clarified a bit. We must distinguish
between:
- a user manual that tells you how to use the system and give you an overview
of the whole system and the most important parts (pictures, math, etc.)
- and a reference manual, that describes all available commands in detail.
The user manual exists (excursion and manual) but has to be revised. The
reference manual exists (http://texshow.contextgarden.net/) but is by far not
complete.
As it is very difficult to make an automated process for producing the user
manual, the candidate for the proposed semiautomatic production is the
reference manual.
Where does the XML-files that are the basis for the existing texshow
applications come from? The production of this file(s) has to be somehow
bound to the current sourcecode. Then at least all commands are present
and "only" the documentation has to be filled in. The last commands I have
learned by asking on this list, are all not present in texshow so that I was
not able to add the description there ...
For the user manual(s) (in my opinion the excursion is a part of "the
manual"), there are these steps necessary:
- provide a sourceversion that works with the current state of context
- identify the portions that are completely out of sync and cut them out (or
mark them clearly as outdated)
- provide pointers to the more current documentation for every part (and mark
differences between mkii and mkiv)
- add the missing main features
and as a bonus to the reference manual:
- make groups of commands that belong together and describe their interactions
(something like the portal pages of wikipedia)
As far as I understand the situation, the completion of the reference manual
is a realistic goal for the near future. And it is possible that everyone
helps with this by filling the answers you get on this list into the command
descriptions.
Wow, this has been gotten longer than I wanted it to be :-)
But let me close with a HUGE big THANK YOU to Hans and Taco and the other
people that make context such a great tool!
Uwe
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-07-28 23:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 23:58 abbg770
2008-07-22 0:37 ` John Culleton
2008-07-25 20:07 ` Gerben Wierda
2008-07-25 22:42 ` luigi scarso
2008-07-25 23:31 ` Aditya Mahajan
2008-07-26 2:38 ` Gerben Wierda
2008-07-27 19:40 ` David
2008-07-28 9:50 ` Gerben Wierda
2008-07-28 10:46 ` Taco Hoekwater
2008-07-28 12:48 ` Gerben Wierda
2008-07-28 12:57 ` Taco Hoekwater
2008-07-28 14:11 ` Aditya Mahajan
2008-07-28 23:07 ` Uwe Koloska [this message]
2008-07-28 14:20 ` Hans Hagen
2008-07-28 15:44 ` Gerben Wierda
2008-07-28 20:36 ` Hans Hagen
2008-07-29 9:02 ` Gerben Wierda
2008-07-29 12:44 ` Aditya Mahajan
2008-07-29 20:01 ` Gerben Wierda
2008-07-29 18:05 ` Hans Hagen
2008-07-29 19:54 ` Gerben Wierda
2008-07-30 16:21 ` Fabrice Popineau
2008-07-31 16:17 ` 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=200807290107.43947.ml@koloro.de \
--to=ml@koloro.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).