public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: Adam Dinwoodie <adam@dinwoodie.org>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Frequent Warning messages using gv
Date: Sat, 8 Oct 2022 09:06:55 -0400	[thread overview]
Message-ID: <fe04552e-abe7-4739-9d81-2aa63ef7ce16@cs.umass.edu> (raw)
In-Reply-To: <CA+kUOanZZ4afMEMUxcKT9CzytC_pv2tAJnUpHYZGvFgL==xpVA@mail.gmail.com>

On 10/8/2022 8:57 AM, Adam Dinwoodie wrote:
> On Wed, 5 Oct 2022 at 06:46, Fergus Daly wrote:
>> Whenever I use gv on a PostScript file as in
>> $ gv filename.ps
>> 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 filename.ps 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*.
> 
> I doubt it. I'm not familiar with gv, but this looks like you're
> trying to process documents that incorporate Helvetica, in a way that
> requires having the font files, without having the font files.
> Helvetica is a trademark, and the font files are under copyright, so
> no Cygwin package is going to be able to include the fonts or even
> include substitutes with matching filenames.
> 
> You *might* be able to add symlinks from the missing Helvetica files
> to more readily available metric-identical alternatives you already
> have access to, e.g. Arial, MS Sans Serif, or Liberation Sans.
> Otherwise I suspect you need to either avoid processing files that
> incorporate fonts you don't own, or buy copies of the relevant
> Helvetica typefaces.

Something I might try first is researching how fontconfig can allow
you to set up substitutions.

Cheers - Eliot Moss

  reply	other threads:[~2022-10-08 13:06 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 [this message]
2022-10-08 13:01 ` Jon Turney
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:
  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=fe04552e-abe7-4739-9d81-2aa63ef7ce16@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=adam@dinwoodie.org \
    --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).