From: David Burgess <dhb@maths.qmw.ac.uk>
To: cygwin@cygwin.com
Cc: d.burgess@qmul.ac.uk
Subject: Ghostscript 8.63-2 fonts problem after upgrade
Date: Mon, 19 Jan 2009 12:39:00 -0000 [thread overview]
Message-ID: <200901190924.n0J9Orf19573@telstar.maths.qmul.ac.uk> (raw)
Hi,
An upgrade of a rather old cygwin installation has resulted
in ghostscript (gs) failing when standard fonts are required
(as some of the standard example files).
However, some postscript files (eg created with LaTeX) are
processed correctly.
clearly a fonts issue, but not clear why the upgrade has
resulted in the standard fonts being the problem, particularly
as search path looks right.
Any pointers - apart from reinstall cygwin? thanks
David Burgess
Example:
bash-3.2$ gs /usr/share/ghostscript/8.63/examples/colorcir.ps
GPL Ghostscript 8.63 (2008-08-01)
Copyright (C) 2008 Artifex Software, Inc. All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Loading NimbusRomNo9L-Regu font from
/usr/share/ghostscript/fonts/n021003l.pfb... Error: /undefined in /findfont
Operand stack:
Times-Roman
etc.
----
bash-3.2$ cygcheck -c | grep gho
ghostscript 8.63-2 OK
ghostscript-fonts-other 6.0-1 OK
ghostscript-fonts-std 8.11-1 OK
$ gs -h
GPL Ghostscript 8.63 (2008-08-01)
Search path:
. : /usr/share/ghostscript/8.63/lib :
/usr/share/ghostscript/8.63/Resource : /usr/share/ghostscript/fonts :
/usr/share/ghostscript/fonts : /usr/share/fonts/TTF :
/usr/share/fonts/Type1
-------------------------------------------------------------------
David Burgess
Astronomy Unit, Queen Mary, University of London, LONDON E1 4NS, UK
Tel: +44 (0)20 7882 5460 Fax: +44 (0)20 8983 3522
D.Burgess@qmul.ac.uk http://www.space-plasma.qmul.ac.uk/
-------------------------------------------------------------------
--
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/
reply other threads:[~2009-01-19 9:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200901190924.n0J9Orf19573@telstar.maths.qmul.ac.uk \
--to=dhb@maths.qmw.ac.uk \
--cc=cygwin@cygwin.com \
--cc=d.burgess@qmul.ac.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).