Re: unencoded characters in printer resident PS fonts

From	ken <ken@spamcop.net>
Newsgroups	comp.lang.postscript
Subject	Re: unencoded characters in printer resident PS fonts
Date	2011-09-22 07:21 +0100
Message-ID	<MPG.28e4e45b3f5fc16a989860@usenet.plus.net> (permalink)
References	<4e7a1248$0$6633$9b4e6d93@newsspool2.arcor-online.net> <9dukm1FpbrU1@mid.individual.net> <4e7a386a$0$7625$9b4e6d93@newsspool1.arcor-online.net> <9dv0daFvt9U1@mid.individual.net>

Show all headers | View raw

In article <9dv0daFvt9U1@mid.individual.net>, h.blischke@acm.org says...
 
> > Since the definition of min is already in the file, I wonder why they
> > still use .min?
> > 
> > best regards
> 
> I suppose they simply forgot to change, since this script obviously mainly 
> is used with Ghostscript.
> You might file a bug at bugs-gs@ghostscript.com

Please file bugs at http://bugs.ghostscript.com 

The address for the mailing list is actually gs-bugs@ but please do not 
send mail there.

FWIW Simply enumerating the CharStrings dictionary of a font is the 
simplest way to render all the glyphs in it. (This won't work for type 
42 fonts)

			Ken

Back to comp.lang.postscript | Previous | Next — Previous in thread | Find similar

Thread

unencoded characters in printer resident PS fonts Plamen Tanovski <pgt@arcor.de> - 2011-09-21 18:35 +0200
  Re: unencoded characters in printer resident PS fonts Helge Blischke <h.blischke@acm.org> - 2011-09-21 19:20 +0200
    Re: unencoded characters in printer resident PS fonts Plamen Tanovski <pgt@arcor.de> - 2011-09-21 21:18 +0200
      Re: unencoded characters in printer resident PS fonts Helge Blischke <h.blischke@acm.org> - 2011-09-21 22:40 +0200
        Re: unencoded characters in printer resident PS fonts ken <ken@spamcop.net> - 2011-09-22 07:21 +0100

csiph-web