X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
From: Hugh Myers <hsmyers AT gmail DOT com>
Date: Tue, 12 May 2009 16:24:30 -0600
Message-ID: <408995400905121524w6f0b4d6ft980a7aff0dbc747c@mail.gmail.com>
Subject: gs--yes, gv--yes, lpr--no Font problems still...
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

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

--hsm

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