|
From: | Knut Petersen |
Subject: | Re: Ghostscript 9.26 cannot embed CID fonts |
Date: | Tue, 19 Mar 2019 19:20:52 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.2 |
On 02.01.19 14:27, Knut Petersen wrote:
On 15.12.18 15:42, Masamichi Hosoda wrote:I've noticed that gs-9.26 cannot embed CID fonts for the extractpdfmark method. In the method, we defined fonts in PostScript, and use it in PDF. gs-9.26 cannot define the fonts for PDF in PostScript. https://bugs.ghostscript.com/show_bug.cgi?id=700367#c4The big problem is that the possible workaround ( use of 'gs -I<path> ...' ) is broken too.
Since a bit more than an hourĀ ghostscript 9.28 has been fixed (commits e005c87e09f6 and eec855c9baea in ghostpdl master). Two workarounds are possible: 1: put the cid fonts in a CIDFont directory and use the -I command line argument 2: define CID fonts in a postscript file and feed that to ghostscript. As an example I give the necessary code for defining a non-standard cid version of Emmentalter-Brace: /lilypond-datadir where { pop } { userdict /lilypond-datadir (/home/knut/sources/lilybuilt/share/lilypond/2.21.0) put } ifelse lilypond-datadir (/fonts/otf/emmentaler-brace.cid) concatstrings (r) file .loadfont /Emmentaler-Brace /CIDFont findresource << exch {} forall /Path lilypond-datadir (/fonts/otf/emmentaler-brace.cid) concatstrings >> /Emmentaler-Brace exch /CIDFont defineresource pop /Emmentaler-BraceĀ /Identity-H [ /Emmentaler-Brace ] composefontĀ pop For details see the discussion in https://bugs.ghostscript.com/show_bug.cgi?id=700436 Knut
[Prev in Thread] | Current Thread | [Next in Thread] |