From: Gerben Wierda <Gerben.Wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: cont-enp.pdf on lulu
Date: Tue, 29 Jul 2008 22:01:56 +0200 [thread overview]
Message-ID: <CAE1A235-245C-4B3D-A81B-90EC4195BCD2@rna.nl> (raw)
In-Reply-To: <alpine.DEB.1.00.0807290825530.21935@nqv-yncgbc>
On Jul 29, 2008, at 2:44 PM, Aditya Mahajan wrote:
> Hi Gerben,
>
> On Tue, 29 Jul 2008, Gerben Wierda wrote:
>
>> This should be based on (imo) merging the content of the excursion
>> and
>> the manual.
>
> Here (and sometime earlier in the thread) you have suggested that
> you find
> the scattered documentation of ConTeXt confusing and would like to
> see an
> exhaustive manual. I agree with that in principle, but still believe
> that
> excursion and the manual should be separate. The manual can be a
> superset
> of excursion, but there needs to be "beginner's manual".
>
> If there is a exhaustive manual, it will be *huge*. An exhaustive
> manual
> on math will be of the size of a book; so would an exhaustive manual
> on
> metapost/mp-lib (think of an updated metafun manual). I can also
> imagine
> an exhaustive manual for fonts to be big (how do we handle fonts for
> lua/xetex/pdftex; how do we handle fonts for different scripts,
> etc.); and
> fairly large manuals for floats (three four mechanism for tables,
> about 20
> ways to move around floats, etc.), critical editions (I don't know the
> status of the proposed module), bib module (the user manual for
> biblatex,
> which is similar in spirit to bib module, is huge), etc.
>
> So, if we want exhaustive documentation and a beginner's
> manual, I see that we only have the option of expanding on the
> excursion
> to have an upto date beginner's manual, expanding on the manual to
> have an
> upto date (but not exhaustive) user manual, and have a series of
> specialized exhaustive manuals. But that will still mean that the
> documentation is scattered.
>
> The way I see it, we can update the documentation, but not really
> solve
> the problem of scattered documentation :-(
Before things balloon to a size it is not feasible anymore, I would
suggest keeping manual&reference apart from introductory documents
like excursion or 'beginners manual'. And I would be very happy if
there was only one decent manual&reference maintained by a group of
people, complete and up to date. thers could maintain a beginner's
manual on the basis of that, but add the maintenance of a second
beginner's manual and suddenly one needs to maintain two things. This
cannot completely be avoided (as also in the manual the same thing
will be in many places as technique 1 is part of the example for
technique 2, etc.).
At first, I would suggest that the documentation project would
consider itself with one thing: a 'user & reference manual' for
ConTeXt. If that succeeds and people have energy left they can do a
simplified beginner's manual.
Note: personally, I think a beginner's manual could be part of the big
manual. Say, an 'excursion' chapter or a 'beginner's section' at the
start of each chapter..
G
___________________________________________________________________________________
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-29 20:01 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
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 [this message]
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=CAE1A235-245C-4B3D-A81B-90EC4195BCD2@rna.nl \
--to=gerben.wierda@rna.nl \
--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).