public inbox for
 help / color / mirror / Atom feed
From: Jon Turney <>
To: Fergus Daly <>,
	The Cygwin Mailing List <>
Subject: Re: Frequent Warning messages using gv
Date: Sat, 8 Oct 2022 14:01:50 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <DB6P18901MB005555B2082D0EB5F86477B7A45D9@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>

On 05/10/2022 06:45, Fergus Daly wrote:
> Whenever I use gv on a PostScript file as in
> $ gv
> then a (usually) successful display is (almost invariably) accompanied by Warning messages about font conversions.
> It is not obvious what limitations or errors are affecting the displayed output, if any, and I have got into the habit
> of issuing the command with the qualifier
> $ gv 2> /dev/null
> However: the Warning messages whilst occasionally very esoteric nearly always include the form
> Warning: Missing charsets in String to FontSet conversion
> Warning: Cannot convert string "-*-Helvetica-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct
> Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-100-*-*-P-*-ISO8859-1" to type FontStruct
> Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct
> Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-140-*-*-P-*-ISO8859-1" to type FontStruct
> Is there some additional fonts package or group of packages that I could usefully incorporate into my Cygwin setup that
> would reduce warnings when using gv? (And maybe improve the rendering of outputs.)
> My directory /usr/share/fonts/microsoft/ contains 120+ ttf links, though none looking anything like helv*.

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?

  parent reply	other threads:[~2022-10-08 13:01 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 [this message]
2022-10-08 17:09   ` Ken Brown
2022-10-09  3:45     ` Brian Inglis
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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