ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Rob Heusdens" <robheus@xs4all.nl>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: State of documentation of ConTeXt?
Date: Mon, 14 Jul 2014 15:03:05 +0200	[thread overview]
Message-ID: <1642f57885676cbd1020027a2bff7c40.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <C888D390-0899-4B03-8AFC-7CBD70114CF4@rna.nl>

Hello G / all

I started using ConText about a year ago. But as a "novice" to Context
(and Tex in general) I can say is that this would be the first thing to
work on, because currently it is a bit of a pain to start using ConText in
any serious way, because there is a lack of up-to-date documentation.

The mailing list here does make a good contribution to explaining things
(I did not use it before, but while the Contextgarden was offline for a
while last week, this was the only place for getting needed info) that the
documentation and contextgarden wiki misses.

But I think a regular user would want to have up-to-date documentation,
and many examples worked out and a whole bunch of ready to use (well
documented) templates/start documents for all kinds of use-cases.

The contextgarden wiki often does not provide well enough information.

There are commands with over 20 different parameters, and the most of them
are not documented at all. So, a novice user can only use the commands in
a trivial sense, but for advanced use the command provides, there is no
documentation on how it is supposed to work.

This is a pitty, because the ConText distribution really offers a lot of
features one want for avanced typesetting jobs, but too often one wants to
understand the behaviour of some command or use the advanced options which
are provided, but can't because the documenation is too poor to make sense
of it.

To look in the source is not a a good replacement for that I guess (only
for advanced users which co-develop ConText).

Well at least the mailing list provides the answers one wants, but it
would be far better I guess if such information would be up-to-date on
contexgarden.

Can we make this a feature request with HIGH priority?

Greetings,

Rob.


> Hello guys,
>
> I am restarting a book project I started a several years back. At that
> time I set up a copy of another project I am working on in ConTeXt, so
> with the products/environment/chapters structure, added Mac fonts to my
> setup, using texexec for compilation.
>
> Now that I am restarting, I am returning to ConTeXt. The first thing I did
> was go to contextgarden and look for updated documentation. What I found
> was the over 10-year old documentation (contextref.pdf) with green boxes
> stating things like “TODO: Add some text about recent developments,
> especially the split between mkii and mkiv”.
>
> Is there up-to-date and reasonably complete ConTeXt documentation these
> days?
>
> G
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>


___________________________________________________________________________________
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-14 13:03 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 [this message]
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

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=1642f57885676cbd1020027a2bff7c40.squirrel@webmail.xs4all.nl \
    --to=robheus@xs4all.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).