From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: PhD Thesis in ConTeXt
Date: Wed, 22 Oct 2008 22:52:38 +0200 [thread overview]
Message-ID: <200810222252.38277.alan.braslau@cea.fr> (raw)
In-Reply-To: <48FEEEAA.2836.003C.0@eumetsat.int>
On Wednesday 22 October 2008 09:13:20 Stephen A. Tjemkes wrote:
> The single frustrating element of context is the documentation. I use
> context now for many years (not on a daily basis though) for writing
> journal papers, posters, presentations etc. I think it is a great package.
> and the community is very active in helping solving problems. But
> documentation is scattered in differnt pdf files, in different places. I
> am aware that writing good documentation (complete and self consistent) is
> time consuming and on first sight not rewarding.
The context manuals need to be updated and completed. The wiki is a good
(dynamic) source of information, but this lacks the structuring of written
manuals. I believe that people are working on this, both trying to structure
the wiki as well as to revise the manuals, unless I am mistaken. Good
documentation is a lot of work, but I believe that it is (almost) as important
as good programming...
My question to the mailing list: is this task structured? Is this being
managed by anyone?
Perhaps this was discussed at the User Meeting last August. I would have liked
to participate (had I been available)...
___________________________________________________________________________________
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-10-22 20:52 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 17:56 Piotr
2008-10-21 18:58 ` Jeff Smith
2008-10-21 19:35 ` Henning Hraban Ramm
2008-10-21 20:32 ` Diego Depaoli
2008-10-21 22:46 ` Marcin Borkowski
2008-10-22 5:31 ` emacs (was: Re: PhD Thesis in ConTeXt) Peter Münster
2008-10-22 6:18 ` Marcin Borkowski
2008-10-22 10:50 ` emacs Gour
2008-10-23 21:08 ` emacs Peter Münster
2008-10-23 22:46 ` emacs Marcin Borkowski
2009-02-05 15:06 ` emacs Peter Münster
2009-02-05 15:19 ` emacs luigi scarso
2009-02-05 19:15 ` emacs Peter Münster
2009-02-11 15:35 ` local footnotes Albrecht Kauffmann
2009-02-13 14:44 ` Thomas Floeren
2009-02-20 8:17 ` Albrecht Kauffmann
2009-02-20 10:28 ` Thomas Floeren
2009-02-24 7:37 ` Albrecht Kauffmann
2009-02-26 19:28 ` rulethickness in columns Albrecht Kauffmann
2009-03-01 18:26 ` Mojca Miklavec
2009-03-01 18:45 ` Hans Hagen
2009-03-02 10:19 ` Wolfgang Schuster
2009-03-02 10:41 ` Hans Hagen
2009-03-03 1:25 ` Wolfgang Schuster
2009-03-03 18:04 ` Wolfgang Schuster
2009-03-03 18:26 ` Hans Hagen
2009-03-03 18:44 ` Wolfgang Schuster
2009-03-03 18:29 ` Hans Hagen
2009-03-03 18:50 ` Wolfgang Schuster
2009-03-02 14:31 ` Mojca Miklavec
2009-03-02 14:58 ` Peter Rolf
2008-10-22 1:24 ` PhD Thesis in ConTeXt Mojca Miklavec
2008-10-22 3:10 ` Aditya Mahajan
2008-10-22 5:41 ` Alan BRASLAU
2008-10-28 1:29 ` Mohamed Bana
2008-10-28 15:20 ` Aditya Mahajan
2008-10-22 7:13 ` Stephen A. Tjemkes
2008-10-22 8:18 ` Steffen Wolfrum
2008-10-22 12:45 ` John Devereux
2008-10-22 18:53 ` Peter Münster
2008-10-22 20:52 ` Alan BRASLAU [this message]
2008-10-22 21:25 ` Aditya Mahajan
2008-10-23 14:37 ` Taco Hoekwater
2008-10-23 14:54 ` John Devereux
2008-10-23 15:38 ` Documentation (Re: PhD Thesis in ConTeXt) Taco Hoekwater
2008-10-23 18:09 ` Rory Molinari
2008-10-23 22:30 ` Marcin Borkowski
2008-10-24 7:18 ` luigi scarso
2008-10-23 21:27 ` documentation, was PhD Thesis in ConTeXt Alan BRASLAU
2008-10-23 22:21 ` Marcin Borkowski
2008-10-22 13:05 Piotr
2008-10-22 13:43 ` Marcin Borkowski
2008-10-23 17:34 ` Jeff Smith
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=200810222252.38277.alan.braslau@cea.fr \
--to=alan.braslau@cea.fr \
--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).