Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!mintaka!think.com!sdd.hp.com!elroy.jpl.nasa.gov!swrinde!ucsd!ucbvax!bloom-beacon!eru!hagbard!sunic!compuram!pgd
From: pgd@bbt.se
Newsgroups: comp.lang.postscript
Subject: Adobe type 1 font seac and CharStrings
Message-ID: <1990Nov17.174853.9476@bbt.se>
Date: 17 Nov 90 17:48:53 GMT
Organization: .
Lines: 30

The following is just for your information, in case you wonder what
will happen if you change the encoding for a type 1 font...


The command "seac" stands for "standard encoding accented character".
In the black book it says that the encoding of the font must use the
standard encoding to be able to use this command.
That is true. Which also means that all adobe type 1 fonts must use
"StandardEncoding".
If you define some other encoding for the type 1 font, and use seac,
the following will happen:
When the seac command is seen, and the characters for the seac are not
cached, it will use the characters according to the standard font
encoding. But if one (or both) characters are found in the font cache,
it will use the encoding that you defined for the font, instead.

The result is a complete mess.


Another statement in the manual is:

       	"Note: The RD, NP, and ND functions must be implemented by
	PostScript language procedures and must be invoked by a single
	name as shown in the program example. These functions may not
	be implemented by equivalent in-line code."

Why this? It seems like that encoding the CharStrings in hex, like in
Ghostscript, works as well. That also have the added benefit that the
font is all ascii format, and the surrounding eexec is not needed.
This also reduces the size of the font to around half.