Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Hannu E K Nevalainen \(garbage mail\)" <garbage_collector AT telia DOT com>
To:	"Joshua Daniel Franklin" <joshuadfranklin AT yahoo DOT com>, <cygwin AT cygwin DOT com>
Subject:	RE: "Using Cygwin Effectively with Windows" -- Draft of new User's Guide section
Date:	Wed, 30 Jul 2003 23:56:15 +0200
Message-ID:	<NGBBLLIAMFLGJEOAJCCEOEFODCAA.garbage_collector@telia.com>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
In-Reply-To:	<20030730181807.56965.qmail@web20007.mail.yahoo.com>
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106
Importance:	Normal

> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of Joshua Daniel Franklin
> Sent: Wednesday, July 30, 2003 8:18 PM

> I've thrown together a prospective "Using Cygwin Effectively with
> Windows"
> section for the User's Guide.
>
> If you'd like to look at it as a web page:
> <http://iocc.com/~joshua/tmp/using-effectively.html>

In the next to last paragraph there is a strange thing ;-)
 "Therefore these two types of links differently."

--8<--
> Some things:
--8<--
> --Documentation of printing is sparse since I don't really do it much.
> Does anyone have extensive documentation of their complex setup?

 I'd say stay basic: i.e. tell that:  (This is quickly sribbled text, take
heed!)

--
"lpr" just sends data to the printer defined in $PRINTER unless told to send
elsewhere with "-P" (man lpr for details). Take note that lpr does
absolutely *NO* conversion of the data.

 For a printer to accept data or text to be printed, the printer must most
of the time be told about the format of the data that is sent to it. Failing
to do so will make the printer either do random things or "hang" at least,
at best it ignores the input.

 Most of the time, unless the printer is real simple, doing things like:
 $ cat ~/.profile | lpr
won't work, just because the output would be plain ASCII/text. while
 $ enscript ~/.profile
would work, assuming you have defined a postscript printer as "default
printer" in Windows. This is so because enscript creates a postscript
wrapper for the text in the file.

 Postcript, for printers capable of that, can be generated with a2ps and
enscript at least. ghostscript has some ablilities in the field of
converting postscript into printer-native data e.g. PCL for HP Deskjet and
Laserjet printers. Then there might be others that might compile OTOB e.g.
djtools from Debian distributions and HP deskjet drivers from RedHat Linux
distributions. Printers from other vendors will require other tools to
generate the data that will cause the printer put output on paper.
--

Anyone; Adjustments for correctness?

/Hannu E K Nevalainen, B.Sc. EE Microcomputer systems - 59?14'N, 17?12'E
--END OF MESSAGE--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -