From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Page Numbering Hell
Date: Sun, 25 Oct 2009 15:57:02 +0100 [thread overview]
Message-ID: <4AE4673E.6020708@wxs.nl> (raw)
In-Reply-To: <1ea4ae670910220103j7d3d027dpc0e5f76644b837d1@mail.gmail.com>
Boštjan Vesnicer wrote:
> for me it is actually very obvious an easy to understand the situation
> about missing documentation. In my opinion there are a couple of
> reasons for that:
> - The gurus don't have time to write the documentation since they have
> more important things to do, i.e. implementing features.
indeed; and since we also have to make a living, sometimes demands of
projects get priority
> - Documentation (in a form of a manual) is of the most value to the
> newbies, but they can't write a manual by themselves about something
> they dont't know much about. So they ask for the documentation on the
> mailing list, but they eventually find out that the up-to-date
> documentation is missing and they start to use other sources of
> information (wiki, mailing list, source code etc.). They learn slowly,
> but at the end (if they persist long enough) they know enough that
> they maybe could write a manual. However, they don't really need the
> manual any more so they decide not to write one. (Paradoxical
> situation, I know.)
good point ... also, writing a manual helps oncovering inconsistencies;
a variant on manuals is writing articles (e.f. for tex user group
magazines)
> - The key is in the motivation. If you want better documentation, you
> have to figure out how to convince the gurus to write one.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-10-25 14:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 6:36 Bryant Eastham
2009-10-21 7:13 ` Alan BRASLAU
2009-10-21 7:46 ` luigi scarso
2009-10-21 14:24 ` Bryant Eastham
2009-10-21 16:00 ` Alan BRASLAU
2009-10-21 16:52 ` Bryant Eastham
2009-10-21 17:42 ` Alan BRASLAU
2009-10-23 7:19 ` Taco Hoekwater
2009-10-23 7:38 ` luigi scarso
2009-10-23 7:45 ` Aditya Mahajan
2009-10-23 20:41 ` Aditya Mahajan
2009-10-26 6:42 ` Thomas Floeren
2009-10-23 7:57 ` luigi scarso
2009-10-24 11:48 ` Spam:*****, " Hans Hagen
2009-10-22 8:03 ` Boštjan Vesnicer
2009-10-25 14:57 ` Hans Hagen [this message]
2009-10-21 15:49 ` Aditya Mahajan
2009-10-23 16:34 ` Bryant Eastham
2009-10-21 20:57 ` Thomas A. Schmitz
2009-10-23 8:30 ` Bryant Eastham
2009-10-23 8:49 ` luigi scarso
2009-10-23 9:39 ` Alan BRASLAU
2009-10-24 11:57 ` Spam:*****, " Hans Hagen
2009-10-23 19:57 ` Page Numbering Hell (SOLVED) Bryant Eastham
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=4AE4673E.6020708@wxs.nl \
--to=pragma@wxs.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).