From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: State of documentation of ConTeXt?
Date: Wed, 23 Jul 2014 14:36:15 +0200 [thread overview]
Message-ID: <1ow9m1o78emvq.dlg@nililand.de> (raw)
In-Reply-To: <D0B26416-4647-47E2-9982-17FC3B2478E2@rna.nl>
Am Sun, 20 Jul 2014 23:07:32 +0200 schrieb Gerben Wierda:
>> 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.
> If a tool needs 50.000 pages to document its use, you are in
> trouble (in more ways than one).
Well imho the LaTeX-documentations could add up easily to this
number, probably more: e.g. source3 has more then 700 pages, tikz
more than 1000, etc.
So imho Mojca's estimate is probably quite sound. But naturally such
a reference is not the same as an introductionary book like the
latex guide or the latex companion. Such books have to select and
layout their informations -- and if it weren't possible to write
such a book about context then you are in trouble.
> I would immediately buy any book that explains ConTeXt such as the
> books that are there for LaTeX. But then, LaTeX is moribund and
> doesn’t change at all. An easier target.
As you wrote in a later posting: many books about latex are in parts
outdated as they couldn't keep up with the development e.g. of tikz,
biblatex, expl3 etc. So I don't see how you can claim that "latex
doesn't change at all".
Beside this I don't believe that context is changing so much that it
would be impossible to write a book about it: I doubt that all the
people who uses context in their daily work would like it if they
had to adapt their document regularly to some new syntax.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2014-07-23 12:36 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
2014-07-23 12:36 ` Ulrike Fischer [this message]
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=1ow9m1o78emvq.dlg@nililand.de \
--to=news3@nililand.de \
--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).