From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: ghostscript issues
Date: Wed, 3 Jun 2020 10:32:48 -0700 [thread overview]
Message-ID: <b6578593-313c-1d0f-8247-fc769718e848@jhmg.net> (raw)
In-Reply-To: <ff08fbf9-7ddf-a037-e596-f186c7994267@cornell.edu>
On 6/3/2020 4:56 AM, Ken Brown via Cygwin wrote:
> It turned out that fixing that one commit was all that was required, but
> the hunk I quoted above wasn't the culprit.
>
> I've just uploaded ghostscript 9.52-2, which should fix the problem
Tested 9.52-2 with ocrmypdf and I can confirm it has solved the problem
here as well.
Thank you!
--
Jim Garrison jhg@acm.org
next prev parent reply other threads:[~2020-06-03 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1604953430.859583.1591025163209.ref@mail.yahoo.com>
2020-06-01 15:26 ` Thomas Bodine
2020-06-01 16:43 ` Ken Brown
2020-06-01 17:48 ` Marco Atzeri
2020-06-02 11:58 ` Lemures Lemniscati
2020-06-02 12:12 ` Ken Brown
2020-06-02 18:14 ` Ken Brown
2020-06-03 11:56 ` Ken Brown
2020-06-03 13:33 ` Lemures Lemniscati
2020-06-03 17:32 ` Jim Garrison [this message]
2020-06-01 21:57 ` Jim Garrison
2020-06-02 19:04 ` Brian Inglis
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=b6578593-313c-1d0f-8247-fc769718e848@jhmg.net \
--to=jhg@jhmg.net \
--cc=cygwin@cygwin.com \
--cc=jhg@acm.org \
/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).