From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Ghostscript cannot find CMaps in Poppler
Date: Mon, 12 Feb 2018 23:14:00 -0000 [thread overview]
Message-ID: <e79312e9-4a9f-2688-3f0d-1c2ef9bbb854@cornell.edu> (raw)
In-Reply-To: <a5e1ec81-2a43-011e-40f5-c7c94e141696@cornell.edu>
On 2/7/2018 5:35 PM, Ken Brown wrote:
> On 2/6/2018 8:40 PM, Vonobow Smith wrote:
>> Â From Cygwin which is bundled with Ghostscript 9.21,
>> Ghostscript cannot find CMap's at all. As a result, CJK characters
>> cannot be rendered at all.
[...]
> Thanks for the report. I'll fix this in a slightly different way with a
> new ghostscript release. It might take a week or so before I can get to
> this.
I've uploaded ghostscript-9.22-3, which should fix this. Please confirm.
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-02-12 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 12:57 [ANNOUNCEMENT] ghostscript 9.22-2 Ken Brown
2018-02-07 1:40 ` Ghostscript cannot find CMaps in Poppler Vonobow Smith
2018-02-07 22:35 ` Ken Brown
2018-02-12 23:14 ` Ken Brown [this message]
2018-02-14 15:56 ` Vonobow Smith
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=e79312e9-4a9f-2688-3f0d-1c2ef9bbb854@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).