To: cygwin@cygwin.com
From: =?ISO-8859-1?Q?Ren=E9_Berber?= <r.berber@computer.org>
Subject:  Re: gs--yes, gv--yes, lpr--no Font problems still...
Date:  Tue, 12 May 2009 17:57:49 -0500
Lines: 22
Message-ID: <gucutf$4sf$1@ger.gmane.org>
References:  <408995400905121524w6f0b4d6ft980a7aff0dbc747c@mail.gmail.com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1
Content-Transfer-Encoding:  quoted-printable
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0
In-Reply-To: <408995400905121524w6f0b4d6ft980a7aff0dbc747c@mail.gmail.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Hugh Myers wrote:

> After getting both gs and gv to find and use the .PFB fonts on my
> system I am now stumped by lpr. I had thought that lpr would use
> ghostscripts font mechanism to resolve font references in a postscript
> file, but apparently not. While both of the other utilities correctly
> find and display the desired font, lpr defaults to some version of
> courier (same thing others did before I found a fix.) Could anyone
> explain this? Don't need much, but do need to be drop-kicked in the
> right direction. Thanks in advance...

lpr uses whatever is the default printer for Windows, if that printer
understands postscript or not, and if the application or driver sends
the fonts or not when needed, is part of the printer configuration.

What usually works with no problem is letting GS control the printing,
that is setting GhostScript as a "port" (with the printer as parameter).

I haven't done this in a long time; very similar to what you do on Unix
to use PS with a plain printer.
--=20
Ren=E9 Berber


--
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/