public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Ghostscript cannot find CMaps in Poppler
Date: Wed, 07 Feb 2018 22:35:00 -0000	[thread overview]
Message-ID: <a5e1ec81-2a43-011e-40f5-c7c94e141696@cornell.edu> (raw)
In-Reply-To: <20180207014036.14303.qmail@mx2.akamoz.jp>

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.
> 
>> $ gsnd
>> GPL Ghostscript 9.22 (2017-10-04)
>> Copyright (C) 2017 Artifex Software, Inc.  All rights reserved.
>> This software comes with NO WARRANTY: see the file PUBLIC for details.
>> GS>/UniJIS-UTF8-H /CMap findresource
>> Error: /undefinedresource in findresource
> 
> This is caused by incorrect setting of search path for Ghostscript,
> or the directory hierarchy of Poppler.
> 
>   GS search path is set as following:
> 
> $ gs --help
>> GPL Ghostscript 9.22 (2017-10-04)
>> Copyright (C) 2017 Artifex Software, Inc.  All rights reserved.
>> Usage: gs [switches] [file1.ps file2.ps ...]
> ... snip ...
>> Search path:
>>     /usr/share/ghostscript/9.22/Resource/Init :
>>     /usr/share/ghostscript/9.22/lib :
>>     /usr/share/ghostscript/9.22/Resource/Font :
>>     /usr/share/ghostscript/fonts : /usr/share/fonts/urw-base35 :
>>     /usr/share/fonts : /usr/share/poppler/cMap/Adobe-CNS1 :
>>     /usr/share/poppler/cMap/Adobe-GB1 :
>>     /usr/share/poppler/cMap/Adobe-Japan1 :
>>     /usr/share/poppler/cMap/Adobe-Japan2 :
>>     /usr/share/poppler/cMap/Adobe-Korea1
> 
> However, CMap files are placed at:
>> $ cd /usr/share/poppler/cMap/Adobe-Japan1/; ls
>> 78-EUC-H                Adobe-Japan1-H-CID   UniHojo-UTF32-H
>> 78-EUC-V                Adobe-Japan1-H-Host  UniHojo-UTF32-V
>> 78-H                    Adobe-Japan1-H-Mac   UniHojo-UTF8-H
> ... snip ...
> 
> The problem is directory hierachy lacks the element "CMap".
> CMap files must be found in CMap directory under the search path, like:
> 
> /usr/share/poppler/cMap/Adobe-Japan1/CMap/UniJIS-UTF8-H
>                                       ^^^^
> The old version of the Ghostscript held CMap's under:
> 
> /usr/share/ghostscript/ver.sion/Resources/CMap
> 
> and this is correct.
> 
> The easiest way to solve this problem is creating symbolic links
> which name is "CMap" in each directories containing CMap files,
> target of the links are the directories itself, like that:
> 
> cd /usr/share/poppler/cMap; for i in *; do (cd $i; ln -s . CMap); done

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.

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

  reply	other threads:[~2018-02-07 22:35 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 [this message]
2018-02-12 23:14     ` Ken Brown
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=a5e1ec81-2a43-011e-40f5-c7c94e141696@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).