From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Finding documentation for ConTeXt
Date: Mon, 28 Jan 2013 18:24:15 +0100 [thread overview]
Message-ID: <B188780E-FF6E-4215-A9E7-E034996BF8AA@web.de> (raw)
In-Reply-To: <alpine.LNX.2.02.1301280921030.4406@ybpnyubfg.ybpnyqbznva>
Hi Aditya,
Thanx for the link.
I have already can across several of the the links on this page/NAV-box(!!),
and bookmark them.
I had notice such boxes before, but considered them to contain database
information and not further links! Learn new things everyday.
One thing is for such I can not get to this page via the ConTeXt Main Page!
At least I think not. (?)
Would be nice if this page was link to from the main page.
Again, many thanx.
regards
Keith.
Am 28.01.2013 um 15:23 schrieb Aditya Mahajan <adityam@umich.edu>:
> On Mon, 28 Jan 2013, Keith J. Schultz wrote:
>
>> My problem is finding decent documentation for ConTeXt.
>>
>> Yes, there is ConTeXt Garden. But, let us be honest it is a big mess.
>> It mixes the old, the bad and the good.
>> I will admit the information there has improved greatly, and
>> YET finding the good and recent is not that easy.
>>
>> Furthermore, since I am interested in what one can and can not
>> do in ConTeXt, I do not know ahead of time exactly what I am looking
>> for. Basically, I literally just stumble over what is good and interesting.
>> That would not be that bad if following the different links would not get
>> one lost and one can not your way back.
>
> See http://wiki.contextgarden.net/Template:Getting_started_navbox
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-01-28 17:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 16:24 \overrightarrow changed Mikael P. Sundqvist
2013-01-27 20:40 ` Hans Hagen
2013-01-27 22:02 ` Otared Kavian
2013-01-28 9:37 ` Finding documentation for ConTeXt Keith J. Schultz
2013-01-28 9:42 ` luigi scarso
2013-01-28 9:58 ` Keith J. Schultz
2013-01-28 14:23 ` Aditya Mahajan
2013-01-28 17:24 ` Keith J. Schultz [this message]
2013-01-28 17:38 ` Mari Voipio
2013-01-28 20:44 ` Keith J. Schultz
2013-01-30 9:00 ` Possible inconsistency in the use of paragraphs in ConTeXt Keith J. Schultz
2013-01-30 9:06 ` Hans Hagen
2013-01-30 15:07 ` Alain Delmotte
2013-01-30 15:08 ` Alain Delmotte
2013-01-30 18:03 ` Keith J. Schultz
2013-01-30 18:13 ` Thomas A. Schmitz
2013-01-30 18:42 ` Alain Delmotte
2013-01-30 18:49 ` Thomas A. Schmitz
2013-01-30 20:14 ` Alain Delmotte
2013-01-31 0:14 ` Keith J. Schultz
2013-01-30 18:28 ` Marco Patzer
2013-01-30 20:56 ` Wolfgang Schuster
2013-01-31 8:40 ` Keith J. Schultz
2013-01-31 16:24 ` Wolfgang Schuster
2013-01-31 22:02 ` Keith J. Schultz
2013-02-01 3:58 ` Wolfgang Schuster
2013-02-01 7:46 ` Alain Delmotte
2013-02-01 7:47 ` Devendra Ghate
2013-02-01 8:34 ` Alain Delmotte
2013-02-01 9:56 ` Keith J. Schultz
2013-01-29 8:43 ` Finding documentation for ConTeXt Hans Hagen
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=B188780E-FF6E-4215-A9E7-E034996BF8AA@web.de \
--to=keithjschultz@web.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).