From: John Culleton <john@wexfordpress.com>
Subject: Re: Context manuals
Date: Fri, 22 Feb 2002 11:01:45 -0500 [thread overview]
Message-ID: <02022211014504.04041@publish> (raw)
In-Reply-To: <KZ437NDv9kd8EwBi@granby.demon.co.uk>
On Friday 22 February 2002 09:02, Bruce Horrocks wrote:
> In message <008901c1badf$fecb6360$6401a8c0@lap>,
>
> on Thu, 21 Feb 2002 at 14:59:25, Frans Goddijn wrote:
> >> >- The question is how to organize this matter:
> >> > through Pragma or W. Egger (BOEDE)?
> >> >Personally I would be interested to set it up.
> >>
> >> www.greatunpublished.com have already
> >> done it.
> >
> >Well they haven't for the manual(s) we are talking about here.
> > That business looks more like an enterprise to sell service to
> > authors who can't find a publisher and are tired of getting their
> > manuscripts returned to them. What we were talking about is not a
> > service that would typeset Hans' manual for him and get it ready
> > for the printer (he's done that better than anyone could) but a
> > service point on both sides of the ocean and eventually on every
> > continent except Antarctica where people can order the printed
> > and nicely bound copy from a TeX user who knows what's actually
> > in the manual
>
> Go and look at their offer again more carefully - that's *exactly*
> what greatunpublished do. They are perfectly able to accept a
> pre-formatted PDF file and print directly from it. The typesetting
> service is only for those that need it (which is probably most of
> their users, admittedly). The only restriction on you is that you
> have to fit to their standard paper size. They take orders from and
> deliver to pretty much anywhere in the world.
>
There is still a problem with all that color printing. The manuals
as currently offered will be beyond the scope of most POD publishers,
and if color is used on very many pages quite expensive. At a minimum
the
chapter headings wold need to be reworked. And the chapter on Color
would make no sense presented in grayscale.
Duplicating at several cent per page in color would also be
costly.
Hopefully Hans Hagen can offer us some guidance when he is available.
>
--
John Culleton, john@wexfordpress.com
Able Indexers and Typesetters
http://wexfordpress.com
<------------------------------------>
next prev parent reply other threads:[~2002-02-22 16:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 19:32 John Culleton
2002-02-20 9:22 ` Patrick Gundlach
2002-02-20 9:28 ` Frans Goddijn
2002-02-20 18:57 ` W. Egger
2002-02-20 23:23 ` Bruce Horrocks
2002-02-21 13:59 ` Frans Goddijn
2002-02-22 14:02 ` Bruce Horrocks
2002-02-22 16:01 ` John Culleton [this message]
2002-02-27 19:26 ` Hans Hagen
2002-02-22 20:09 ` John Culleton
2002-02-21 9:11 ` Taco Hoekwater
2002-02-22 17:39 ` John Culleton
2002-02-20 17:52 ` Frans Goddijn
2002-02-25 13:58 ` Hans Hagen
2002-02-25 16:16 ` Frans Goddijn
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 8:59 [NTG-context] " Hans Hagen
2002-10-22 23:23 ` Hans Hagen
2002-10-23 19:15 ` Henning Hraban Ramm
2002-10-23 22:00 ` Hans Hagen
1999-11-22 8:08 Berend de Boer
1999-11-22 6:47 Zeljko Vrba
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=02022211014504.04041@publish \
--to=john@wexfordpress.com \
/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).