ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: State of documentation of ConTeXt?
Date: Mon, 21 Jul 2014 09:07:58 +0600	[thread overview]
Message-ID: <C7334EA8-D5E4-4659-B95C-4DB266F8B769@fiee.net> (raw)
In-Reply-To: <D0B26416-4647-47E2-9982-17FC3B2478E2@rna.nl>

Am 2014-07-21 um 03:07 schrieb Gerben Wierda <gerben.wierda@rna.nl>:

>> 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 …)
> 
> If a tool needs 50.000 pages to document its use, you are in trouble (in more ways than one). 
> 
> I think in reality a set of manuals, with core functionality and all kinds of extras a manual of 500 pages and maybe a reference manual of the same size would be something useful and thus meaningful. Stuff like MetaFun can have its own manual and doesn’t need to be in a core ConTeXt manual.
> 
> A user manual is enough. You don’t need a developer manual. So, documenting all the development you can do with ConTeXt (programming in lua and whatnot) would for me not be what is needed for a user manual. What a user manual does is what cont-en.pdf does, but then up to date and complete.

If I might chime in …

What we really need (and what „simple“ users like me cannot write, even if I sometimes look into the sources) is a usable command reference, covering all „usable“ commands and all their „usable“ options (i.e. omit too experimental stuff).
What we have on the wiki now is much too incomplete in all regards. I don’t know if there’s something (more?) that can be automated.

I don’t know if Hans, Taco or Wolfgang (any other candidates?) would be able and willing to do that work, if e.g. DANTE would fund it. Would you, and what do you think how much funding would be required to at least document the current state of MkIV?

I would not try to write a (printed/printable) reference manual for ConTeXt, that really makes not much sense.
We don’t need to argue about page estimates, that depends too much on layout anyway …

I thought the previous ConTeXt meeting was about documentation? Didn’t you agree on a better wiki structure?


Greetlings, Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2014-07-21  3:07 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
2014-07-20 21:07             ` Gerben Wierda
2014-07-21  3:07               ` Henning Hraban Ramm [this message]
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=C7334EA8-D5E4-4659-B95C-4DB266F8B769@fiee.net \
    --to=texml@fiee.net \
    --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).