[gs-bugs] [Bug 698730] - Ghostscript - Can't find CID font "Courier New"

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698730

Bug ID: 698730
Summary: Can't find CID font "Courier New"
Product: Ghostscript
Version: 9.18
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P4
Component: Font API
Assignee: ***@artifex.com
Reporter: ***@qq.com
QA Contact: gs-***@ghostscript.com
Word Size: ---

while command:gs wKgJglm-4v-ANWXhAAPt83WR3OI713.pdf
error：Can't find CID font "Courier New"

edit /usr/share/ghostscript/9.18/Resource/Init/cidfmap：
/Courier New << /FileType /TrueType /Path
(/usr/share/ghostscript/fonts/Courier New.ttf) /SubfontID 0 /CSI [(GB1) 2] >>
;

run command:gs wKgJglm-4v-ANWXhAAPt83WR3OI713.pdf again

still error:
While reading gs_cidfm.ps:
Error: /undefined in New

I find it can't recognize spacing in Courier New，whatI can do for this
bug,it's the format wrong or?

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698730

nihao2112 <***@qq.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@qq.com

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698730

Chris Liddell (chrisl) <***@artifex.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Chris Liddell (chrisl) <***@artifex.com> ---
The first element in the "record" is a Postscript name, and Postscript names a
delineated by spaces, so obviously a name with whitespace can't be used
directly.

You have to define it as a string (which Ghostscript will internally convert to
a name, in this case), thus:

(Courier New) << /FileType /TrueType /Path
(/usr/share/ghostscript/fonts/Courier New.ttf) /SubfontID 0 /CSI [(GB1) 2] >>
;

Note that in the cidfmap we ship that is mentioned in the comments at the top
of the file - if that has been removed in your distro case, I'd complain to the
maintainers.

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698730

--- Comment #2 from nihao2112 <***@qq.com> ---
(In reply to Chris Liddell (chrisl) from comment #1)

Post by b***@artifex.com
The first element in the "record" is a Postscript name, and Postscript names
a delineated by spaces, so obviously a name with whitespace can't be used
directly.
You have to define it as a string (which Ghostscript will internally convert
(Courier New) << /FileType /TrueType /Path
(/usr/share/ghostscript/fonts/Courier New.ttf) /SubfontID 0 /CSI [(GB1) 2]

;

Note that in the cidfmap we ship that is mentioned in the comments at the
top of the file - if that has been removed in your distro case, I'd complain
to the maintainers.

it can recognize the font as you set,but make command with convert
wKgJglm-4v-ANWXhAAPt83WR3OI713.pdf w.png still appear gibberish，why？the pdf i
gs contain font about Arial and Courier New.what i set is，what the problem：

/STSong-Light << /FileType /TrueType /Path
(/usr/share/ghostscript/9.18/Resource/CIDFSubst/DroidSansFallback.ttf)
/SubfontID 0 /CSI [(GB1) 2] >> ;
/Arial << /FileType /TrueType /Path (/usr/share/ghostscript/fonts/ARIAL.TTF)
/SubfontID 0 /CSI [(GB1) 2] >> ;
/LiSu << /FileType /TrueType /Path
(/usr/share/ghostscript/9.18/Resource/CIDFSubst/DroidSansFallback.ttf)
/SubfontID 0 /CSI [(GB1) 2] >> ;
/SimSun << /FileType /TrueType /Path (/usr/share/fonts/chinese/SIMSUN.TTC)
/SubfontID 0 /CSI [(GB1) 2] >> ;
/SimHei << /FileType /TrueType /Path (/usr/share/fonts/chinese/SIMHEI.TTF)
/SubfontID 0 /CSI [(GB1) 2] >> ;
/KaiTi << /FileType /TrueType /Path (/usr/share/fonts/chinese/SIMKAI.TTF)
/SubfontID 0 /CSI [(GB1) 2] >> ;
/FZLanTingHeiS-UL-GB << /FileType /TrueType /Path
(/usr/share/fonts/chinese/FZLTCXHJW.TTF) /SubfontID 0 /CSI [(GB1) 2] >> ;
/NSimSun << /FileType /TrueType /Path (/usr/share/fonts/chinese/SIMSUN.TTC)
/SubfontID 0 /CSI [(GB1) 2] >> ;
/MicrosoftYaHei << /FileType /TrueType /Path
(/usr/share/fonts/chinese/MSYH.TTF) /SubfontID 0 /CSI [(GB1) 2] >> ;
/FangSong << /FileType /TrueType /Path (/usr/share/fonts/chinese/SIMFANG.TTF)
/SubfontID 0 /CSI [(GB1) 2] >> ;
/NimbusMono-Regular << /FileType /TrueType /Path
(/usr/share/ghostscript/9.18/Resource/Font/NimbusMono-Regular) /SubfontID 0
/CSI [(GB1) 2] >> ;
/NimbusSanL-Reg << /FileType /TrueType /Path
(/usr/share/ghostscript/9.18/Resource/Font/NimbusSanL-Reg) /SubfontID 0 /CSI
[(GB1) 2] >> ;
/StandardSymL << /FileType /TrueType /Path
(/usr/share/ghostscript/9.18/Resource/Font/StandardSymL) /SubfontID 0 /CSI
[(GB1) 2] >> ;
/NimbusRomNo9L-Reg << /FileType /TrueType /Path
(/usr/share/ghostscript/9.18/Resource/Font/NimbusRomNo9L-Reg) /SubfontID 0
/CSI [(GB1) 2] >> ;
/ArialMT << /FileType /TrueType /Path
(/usr/share/ghostscript/9.18/Resource/Font/ArialMT) /SubfontID 0 /CSI [(GB1)
2] >> ;
/Impact << /FileType /TrueType /Path (/usr/share/fonts/msttcore/impact.ttf)
/SubfontID 0 /CSI [(GB1) 2] >> ;
/CourierNew /Courier ;
/MongolianBaiti /Helvetica ;
(Courier New) << /FileType /TrueType /Path
(/usr/share/ghostscript/fonts/Courier New.ttf) /SubfontID 0 /CSI [(GB1) 2] >>
;

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698730

--- Comment #3 from Chris Liddell (chrisl) <***@artifex.com> ---
That's what happens when you use an incompatible substitute for a CIDFont -
that's why both Adobe and we say that it is *strongly* advised to embed
CIDFonts, and *not* rely on substitution.

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698730

--- Comment #4 from nihao2112 <***@qq.com> ---
(In reply to Chris Liddell (chrisl) from comment #3)

Post by b***@artifex.com
That's what happens when you use an incompatible substitute for a CIDFont -
that's why both Adobe and we say that it is *strongly* advised to embed
CIDFonts, and *not* rely on substitution.

i was put the fonts in one of the search paths, but it can't find out,how to
embed

Post by b***@artifex.com
CIDFonts ???

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698730

--- Comment #5 from Chris Liddell (chrisl) <***@artifex.com> ---
Embedding the CIDFont has to happen when the Postscript/PDF file is created
from the original source. Once the glyph mapping information is lost, it cannot
really be recovered.