From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Frequent Warning messages using gv
Date: Sat, 8 Oct 2022 21:45:17 -0600 [thread overview]
Message-ID: <c93cd1fc-7193-d460-9fa1-8f8659f9d138@SystematicSw.ab.ca> (raw)
In-Reply-To: <0f2be837-c170-1c24-8b52-ac57761f9518@cornell.edu>
On Sat, 8 Oct 2022 13:09:47 -0400, Ken Brown wrote:
> On 10/8/2022 9:01 AM, Jon Turney wrote:
>> Installing 'xorg-x11-fonts-dpi75' and/or 'xorg-x11-fonts-dpi100' will
>> probably resolve these warnings.
>> It's unclear to me if gv needs a dependency on more font packages or
>> not, since the PS could be using any fonts?
> I could go either way on this. On the one hand, gv is a postscript
> viewer and has no control over what fonts it might be asked to
> display. On the other hand, gv is intended to be run under X11, so
> maybe it should require the most basic X11 fonts.
gv requires ghostscript which requires ghostscript-fonts-other and
urw-base35-fonts which should provide a fallback from Helvetica to Nimbus.
Perhaps for older apps and documents urw-base35-fonts-legacy could or
should (also) be included?
Could that solve the problem, or would it still require
xorg-x11-fonts-dpi{75,100)?
--
La perfection est atteinte,
non pas lorsqu'il n'y a plus rien à ajouter,
mais lorsqu'il n'y a plus rien à retirer.
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2022-10-09 3:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 5:45 Fergus Daly
2022-10-08 12:57 ` Adam Dinwoodie
2022-10-08 13:06 ` Eliot Moss
2022-10-08 13:01 ` Jon Turney
2022-10-08 17:09 ` Ken Brown
2022-10-09 3:45 ` Brian Inglis [this message]
2022-10-08 19:22 ` Fergus Daly
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=c93cd1fc-7193-d460-9fa1-8f8659f9d138@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).