Path: csiph.com!weretis.net!feeder6.news.weretis.net!panix!.POSTED.panix1.panix.com!not-for-mail From: rodd@panix.com (Rod Dorman) Newsgroups: comp.lang.postscript Subject: Re: PC Encoding (why some doesn't work?) Date: Thu, 29 Jul 2021 18:44:01 -0000 (UTC) Organization: Public Access Networks Corp. Message-ID: References: <1627514187.bystand@zzo38computer.org> <1627574054.bystand@zzo38computer.org> Injection-Date: Thu, 29 Jul 2021 18:44:01 -0000 (UTC) Injection-Info: reader1.panix.com; posting-host="panix1.panix.com:166.84.1.1"; logging-data="13634"; mail-complaints-to="abuse@panix.com" X-Newsreader: trn 4.0-test77 (Sep 1, 2010) Xref: csiph.com comp.lang.postscript:3656 In article <1627574054.bystand@zzo38computer.org>, wrote: >ken wrote: >> Have you checked the font to see if it contains glyph descriptiosn >> identified with those names ? > >It look like it doesn't include these names. (All of the other glyphs I >specified in the PCEncoding are working, though.) > >> Since these are unusual glyphs, almost certainly the font doesn't >> contain them. > >Would you be able to tell me then what is the proper glyph names for PC >Encoding? If they are the glyphs that this font does not include, which >font does have it, and does Ghostscript include it? (And if not, should >Ghostscript include it?) What do you mean by "PC encoding"? If you want to see what glyph names a font has defined look in its .AFM (Adobe Font Metrics) file -- -- Rod -- rodd(at)polylogics(dot)com