From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: annoying ghostscript output in recent v9.24
Date: Wed, 12 Sep 2018 17:26:00 -0000 [thread overview]
Message-ID: <2141202f-7689-0a6d-1af7-ff55680acbcc@cornell.edu> (raw)
In-Reply-To: <20180912170200.GA1168@ingber.com>
On 9/12/2018 1:02 PM, Lester Ingber wrote:
> I was using ps2pdf
I think you'll have to supply more details for those of us who aren't
familiar with ICC profiles. I know from upstream bug reports that
gs-2.24 has problems with them, and I can go ahead and build gs-2.25
from the release candidate, but I can't test whether it fixes the
problem unless you give a recipe for reproducing the problem.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-09-12 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 17:02 Lester Ingber
2018-09-12 17:26 ` Ken Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-12 17:51 Lester Ingber
2018-09-12 18:17 ` Ken Brown
2018-09-12 16:09 Lester Ingber
2018-09-12 16:19 ` Ken Brown
2018-09-12 16:33 ` Marco Atzeri
2018-09-12 15:09 Lester Ingber
2018-09-12 15:31 ` Marco Atzeri
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=2141202f-7689-0a6d-1af7-ff55680acbcc@cornell.edu \
--to=kbrown@cornell.edu \
--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).