From: David Rogers <davidandrewrogers@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: spacing before items
Date: Tue, 23 Jun 2020 14:18:28 -0700 [thread overview]
Message-ID: <s0ewo3xa3bv.fsf@gmail.com> (raw)
In-Reply-To: <SN6PR11MB257625A7FBE57A5902EBEBC9BD9A0@SN6PR11MB2576.namprd11.prod.outlook.com> (Mike Cooper's message of "Wed, 17 Jun 2020 15:13:11 +0000")
Mike Cooper <mike@murchisondrillingschools.com> writes:
> Thanks Tomáš!
>
> 1. Where can this solution be found?
Mike, I know how you feel. The reasons that the documentation is
so sparse and difficult to find are the same reasons behind a lot
of things: time, money, and ability. Good documentation requires
all three of those things to be brought together at the same time.
Some people reading and responding here have two out of the three,
but it's rare to find someone who has all three at the same time.
On second thought, there are at least five things required: time,
money, ability, desire, and a workable plan. And with ConTeXt
being developed by a relatively tiny group, even if a brilliant
and kind organizer came along and said "I want excellent
documentation for ConTeXt, and I'll pay a fortune to the person
who knows how to write it - see, here's the money" - there's no
way of guaranteeing that someone would actually take the offer.
--
David
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-06-23 21:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 17:51 Mike Cooper
2020-06-16 19:13 ` Wolfgang Schuster
2020-06-17 15:04 ` Mike Cooper
2020-06-17 19:50 ` Mike Cooper
2020-06-17 20:26 ` Henning Hraban Ramm
2020-06-17 20:34 ` Mike Cooper
2020-06-17 20:44 ` Wolfgang Schuster
2020-06-17 21:03 ` Mike Cooper
2020-06-17 21:14 ` Hans Hagen
2020-06-16 19:18 ` Tomas Hala
2020-06-17 15:13 ` Mike Cooper
2020-06-23 21:18 ` David Rogers [this message]
2020-06-23 22:00 ` Mike Cooper
2020-06-24 6:49 ` Hans Hagen
2020-06-24 17:41 ` Mike Cooper
2020-06-24 20:19 ` Henning Hraban Ramm
2020-06-24 21:11 ` Mike Cooper
2020-06-24 21:42 ` Henning Hraban Ramm
2020-06-25 18:28 ` David Rogers
2020-06-29 14:46 ` Mike Cooper
[not found] <mailman.342.1592329885.1283.ntg-context@ntg.nl>
2020-06-16 19:29 ` jkitz
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=s0ewo3xa3bv.fsf@gmail.com \
--to=davidandrewrogers@gmail.com \
--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).