ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: State of documentation of ConTeXt?
Date: Sun, 20 Jul 2014 22:24:10 +0200	[thread overview]
Message-ID: <CALBOmsZ5pgvfbkRbjYd3YQJ8YXFMdBa=Fm7fWti4VihrGSOnVg@mail.gmail.com> (raw)
In-Reply-To: <C16C2786-06E4-49B3-9534-3AF26E19341F@rna.nl>

On Sun, Jul 20, 2014 at 2:14 PM, Gerben Wierda wrote:
>
> Sorry, you can’t expect users to be able to do that. Lamport
> created LaTeX *and* wrote the “LaTeX User’s Guide and Reference manual”.

<teasing>
Indeed. Sorry, you can't do that to users. Christian Schenk also
created MikTeX (I still have MikTeX files from 23 years ago) *and* is
still developing it actively and answering emails from users.
</teasing>

> The authors mentioned below were all developers too. You need that level of
> understanding to write a manual.

What kind of developers? Did they contribute to the LaTeX core? (Many
ConTeXt users are developers, but it highly depends what you count as
a developer.)

>> The project could easily employ two people to work full
>> time just to keep up with the pace of development (once they would
>> catch up).
>
> I would expect it to be far less than that once you have the documentation.

(a) You probably never tried to follow how fast ConTeXt is being developed.
(b) There's a tricky "once" in the sentence.

Ad (a): I've heard a rumour (that might just as well be false
information) that authors of the LaTeX companion or maybe LaTeX
Graphics companion had a serious problem. They hardly managed writing
as fast as the packages described in the book kept developing.

Also, if I see correctly, the book "Guide to LaTeX" has been published
in 2003. Even for LaTeX that's "a totally outdated book" and doesn't
even scratch the surface of LuaTeX, XeTeX and OpenType fonts - the
most useful things that most users should switch to nowadays. The
LaTeX Companion is probably even more outdated and "useless" as it
doesn't even scratch the surface of many useful packages that surfaced
since the last release. I have the LaTeX Graphics Companion on my
bookshelf for example, but even if I was still using LaTeX, the book
would be almost useless to me nowadays. Almost none of the things I
would want to use are covered there (starting with TikZ for example).

The beginner's tutorial for ConTeXt is no more outdated than these
books are (but of course these books were more complete at the time of
writing and probably went under many more proofreading than the
ConTeXt tutorial, with "professional writers" involved).

I'm exaggerating a bit on purpose. But not much.

> Hans & Taco: how much money would need to be raised to produce something of
> the quality of Kopka & Daly’s “Guide to LaTeX”?  or Goossens, Mittelbach &
> Samarin’s “The LaTeX Companion”?

What do you mean with "of the quality of these books"? Having a
similar number of pages written in comparable quality (something like
a revised beginner's manual) or so complete in description of the
functionality as the mentioned manuals?

My estimate would be that a complete context reference with
well-described options and including trivial examples would require
cca. 10.000-50.000 pages. Maybe others have different estimates, but
now do the math. (Existing manuals like MetaFun or the old cont-en.pdf
are roughly 400 pages. But that's nowhere near 10 % of the ConTeXt
functionality. One would need to document the whole TeX part, the
whole metapost part, the whole lua part, the whole xml, all perl, ruby
and lua scripts, write better man pages, probably list the whole
Unicode to show the ConTeXt names in one appendix ...)

> Because, I don’t think this will happen
> unless some money is raised to pay for it.

> I would gladly donate in a crowdfunding initiative for a good book. But how
> much is needed to make it happen?

I would gladly donate as well. But probably not anywhere near the
amount that would suffice even if a nontrivial number of users
contributed the same.

Mojca

PS: the example you linked to asks for 30 EUR for a 220 page book. If
the same calculation is applied to my estimate of the number of
required pages, 22.000 pages would translate to 3000 EUR per copy.
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2014-07-20 20:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 12:18 Gerben Wierda
2014-07-14 13:03 ` Rob Heusdens
2014-07-14 17:29   ` Hans Hagen
2014-07-15  9:59     ` Gerben Wierda
2014-07-15 14:42       ` Mojca Miklavec
2014-07-16 11:24         ` Rob Heusdens
2014-07-16 12:14         ` Alan BRASLAU
2014-07-16 15:08           ` Russ Urquhart
2014-07-16 15:20             ` Hans Hagen
2014-07-16 15:23               ` luigi scarso
2014-07-17 16:28             ` Mica Semrick
2014-07-15 14:55       ` luigi scarso
2014-07-15 15:33         ` Yuri Teixeira
2014-07-15 20:08           ` Hans Hagen
2014-07-15 20:23       ` Hans Hagen
2014-07-15 22:26       ` David Wooten
2014-07-15 22:54         ` Hans Hagen
2014-07-15 23:10           ` David Wooten
2014-07-16  6:30           ` Gour
2014-07-20 12:14         ` Gerben Wierda
2014-07-20 14:55           ` Gerben Wierda
2014-07-20 20:24           ` Mojca Miklavec [this message]
2014-07-20 21:07             ` Gerben Wierda
2014-07-21  3:07               ` Henning Hraban Ramm
2014-07-23 12:36               ` Ulrike Fischer

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='CALBOmsZ5pgvfbkRbjYd3YQJ8YXFMdBa=Fm7fWti4VihrGSOnVg@mail.gmail.com' \
    --to=mojca.miklavec.lists@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).