From: "John R. Culleton" <john@wexfordpress.com>
Subject: Re: A new manual
Date: Fri, 29 Sep 2006 13:00:19 -0400 [thread overview]
Message-ID: <200609291300.19859.john@wexfordpress.com> (raw)
In-Reply-To: <22af238a0609290719l4ceed250m171555be4bf793e3@mail.gmail.com>
On Friday 29 September 2006 10:19, gnwiii@gmail.com wrote:
> On 9/28/06, John R. Culleton <john@wexfordpress.com> wrote:
> > What is needed now for greater acceptance of Context is not new
> > features but a new manual, perhaps a multi volume set with a
> > common index. The 2001 manual is great, but many of the features
> > discussed daily here are not in it. One must chase around the
> > wiki and the individual manuals like "details", and that is not
> > satisfactory from the point of view of the new user. Most of us
> > have memorized the locations of key information but newcomers
> > have not.
>
> I don't agree that lack of a current manual is a big problem for
> potential users of ConteXt. In my experience, the biggest problem is
> with the 3rd party tools (perl, ghostscript, ruby) on Win32 and legacy
> commercial unix (where ruby is not provided and the system perl will
> be a very old version).
>
Interesting. There are minimal Context distros for each of the
major platforms. Does the Win verson include the missing
compilers?
> You can write simple LaTeX documents without working 3rd party tools
> (MikTeX-2.5 seems to provide ghostscript), but you need perl and ruby
> before you can format anything in ConTeXt. There should be some tools
> to check the functioning and versions of ghostscript, perl, and ruby.
> A VMWare player appliacance might be helpful for people with current
> Win32 systems (e.g., ample CPU, disk, and RAM).
>
> > If a consolidated manual set were offered for sale there would be a
> > lot of customers. Or an abridged version, something like the
> > 1999 Excursion manual but expanded and updated, would be a
> > possibility.
>
> Any printed manual will soon become stale. What is needed is an
> introductory manual
> for new users together with an ongoing process to provide current
> information. The wiki is a good start, but there needs to be more
> effort to ensure that the sources can be used as the definitive
> manual. The introductory manual should devote considerable space to
> explaining how to find current information in the wiki and or using
> the source files.
My preferences in order are printed book, downloadable source,
downloadable pdf and online anything. Information needs to be
structured, indexed, portable, easily readable.
--
John Culleton
Able Indexing and Typesetting
Precision typesetting (tm) at reasonable cost.
Satisfaction guaranteed.
http://wexfordpress.com
next prev parent reply other threads:[~2006-09-29 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 13:20 John R. Culleton
2006-09-28 14:42 ` Nikolai Weibull
2006-09-28 16:42 ` Marcus Vinicius Mesquita de So
2006-09-28 18:54 ` Alexander Lazic
2006-09-29 7:09 ` Ricard Roca
2006-09-29 14:19 ` gnwiii
2006-09-29 17:00 ` John R. Culleton [this message]
2006-10-29 12:57 ` Geoffrey Alan Washburn
2006-11-01 17:52 ` Printing ConTeXt books on Lulu? (Was: A new manual) Geoffrey Alan Washburn
2006-11-01 18:19 ` Matthias Weber
2006-11-01 19:07 ` Geoffrey Alan Washburn
2006-09-29 20:09 ` A new manual Hans Hagen
2006-10-04 23:21 ` Aditya Mahajan
2006-10-05 6:51 ` Taco Hoekwater
2006-10-02 17:09 ` fdu.xiaojf
2006-09-29 7:57 A new Manual Fidel Viegas
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=200609291300.19859.john@wexfordpress.com \
--to=john@wexfordpress.com \
--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).