ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: stappers@stappers.nl (Geert Stappers)
Subject: Re: Manual or Book
Date: Mon, 13 Mar 2006 23:52:31 +0100	[thread overview]
Message-ID: <20060313225231.GB29071@gpm.stappers.nl> (raw)
In-Reply-To: <200603101832.59483.john@wexfordpress.com>


[-- Attachment #1.1: Type: text/plain, Size: 981 bytes --]

On Fri, Mar 10, 2006 at 06:32:59PM -0500, John R. Culleton wrote:
> On Friday 10 March 2006 13:29, Jeffrey Drake wrote:
> > I have heard a bit of talk about 'if the manual is updated' or some
> > such like that. I was going to have the manual printed in a book so I
> > have a hardcopy. Is the manual still current and relevant that it
> > would be worth it?
> >
> 
> The manual is five years old. the pattern has been to issue
> additional documentation rather than update the "big" manual. 
> I printed mine out, have it in my manual rack, and it is getting
> worn out from use. 

Worn out from use is one of the better things that can happen to a manual.

> You may as well print it out.
> I have not heard of a new edition pending.  


Mmmm, I'm also looking for a printed edition of the ConTeXt manual.

Does this ML have publishers subscribed that have some VC to burn?
Or does see someone else see a possibilty for a ConTeXt book?


Geert Stappers

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2006-03-13 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 18:29 Manual Jeffrey Drake
2006-03-10 23:32 ` Manual John R. Culleton
2006-03-13 22:52   ` Geert Stappers [this message]
2006-03-13 23:05     ` Manual or Book Steve Peter

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=20060313225231.GB29071@gpm.stappers.nl \
    --to=stappers@stappers.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).