ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: upto current
Date: Wed, 20 Mar 2013 09:49:13 +0100	[thread overview]
Message-ID: <51497809.7010306@wxs.nl> (raw)
In-Reply-To: <2F2ABC1E-124E-424D-94B4-E3CBF448E88A@web.de>

On 3/20/2013 9:12 AM, Keith J. Schultz wrote:
> Hi Hans, All,
>
>
> The biggest crux in using ConTeXt is its documentation.
> True, things have gotten a lot better in the past year!
>
> Yet, there is no ONE definitive place to get comprehensive
> and EASY to find documentation.
>
> 	1) Garden is really not that easy to navigate
> 	2) Garden is loaded with a mixture of mkii and mkiv
>              and it is not always clear if the page one is on is for
> 	    mkii or mkiv or quite outdated.

i wonder how easy it is to split that ... we could move mkii stuff to s 
separate place (or always at the bottom below a "MKII" subtitle)

> 	3) PRAGMA does have up to date manuals.
> 	4) These manuals are quite unfinished in many parts,
>               as are all many of the older manuals.
>
>                   Very frustrating

Most of the old manuals are not that faulty. Maybe incomplete with 
respect to the latest features, but most in it should still work.

With respect to unfinished: yesterday i wondered if I should put the 
intermediate but unfinished font manual on the website but it looks like 
I can better not do that.

> 	5) The newer manuals should be part of the standalone.
>               ( I hate going online to look for a manual when it
>                 should be installed already)

Up to others.

> 	6) Reference manuals are fine for the advanced user, but for
> 	    the beginner or intermediate they are not much help.
>              Especially, if if one does not understand TeX, or Typesetting,
> 	    and one really does not need to use all those options.

That's up to users ... it has been said before, but this is where the 
internet backfires: a lot of tex tutorials started out as articles i.e. 
users writing down experiences. I simply have no more time left to write 
down more than I do now.

> My suggestion would be to have garden have a manuals download
> area where one can get the up to date manuals from Pragma and
> where one can discern how old the others are. It should be also, easy to find.

So maybe you can help Mojca with that .. someone needs to do it and keep 
doing it (descriptions, copies cq. links, etc.).

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2013-03-20  8:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 18:16 Hans Hagen
2013-03-19 18:47 ` Aditya Mahajan
2013-03-19 19:05   ` Hans Hagen
2013-03-20  1:52     ` Aditya Mahajan
2013-03-20  6:05   ` Otared Kavian
2013-03-20  8:05     ` Meer H. van der
2013-03-20  8:19     ` Keith J. Schultz
2013-03-20  8:40     ` Hans Hagen
2013-03-20  9:27       ` Mojca Miklavec
2013-03-20  9:37         ` Hans Hagen
2013-03-20  8:12 ` Keith J. Schultz
2013-03-20  8:25   ` Marcin Borkowski
2013-03-20 17:54     ` Keith J. Schultz
2013-03-21 10:19       ` Mojca Miklavec
2013-03-21 10:32         ` Alan BRASLAU
2013-03-21 14:26           ` Marcin Borkowski
2013-03-22  7:31             ` Keith J. Schultz
2013-03-22  8:26               ` command reference (was: upto current) Peter Münster
2013-03-22 10:11                 ` Procházka Lukáš Ing. - Pontex s. r. o.
2013-03-22 10:25                   ` command reference Peter Münster
2013-03-22 12:04                   ` Hans Hagen
2013-03-22 14:42                   ` command reference (was: upto current) Sietse Brouwer
2013-03-22 16:07                     ` Sietse Brouwer
2013-03-22 17:21                       ` command reference Hans Hagen
2013-03-24 21:48                         ` Sietse Brouwer
2013-03-25  9:42                       ` command reference (was: upto current) Keith J. Schultz
2013-03-25  9:34                 ` Keith J. Schultz
2013-03-22 14:19               ` upto current Bill Meahan
2013-03-22 14:32                 ` Taco Hoekwater
2013-03-22 14:37                   ` luigi scarso
2013-03-22 14:47                 ` Hans Hagen
2013-03-25  8:02                 ` Keith J. Schultz
2013-03-20  8:49   ` Hans Hagen [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=51497809.7010306@wxs.nl \
    --to=pragma@wxs.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).