RE: [Devel] CFF fonts assume Type 2 charstrings

[Graham Asher]

George Williams wrote:

<<<<<<
If the FreeType charstring parser is like PfaEdit's, this is almost
irrelevant. I use the same code to parse type1&2 strings. Almost all of the
differences between the two are codes defined in one but not the other,
there are very few codes where there is a sematic difference between the
two...
>>>>>>

Now this is very interesting. I suspected that might be the case. This means
that the Types 1 and 2 charstring parsers could be merged and put into the
common PostScript-font module (psaux?). A call to the parser could select
type 1 or 2 by means of a new argument. That would save code and make my
life easier.

The background to this is that I am writing a GhostScript-to-FreeType bridge
for Artifex. It has to handle incrementally defined fonts, which is what
motivated my recent changes to FreeType. So far I have got Type 42 and Type
1 fonts working, and am figuring out how to deal with Type 2. GhostScript
treats Type 2 fonts identically to Type 1 fonts internally, except for the
difference in chartrsing type.

Tom, what is your opinion? I guess that you are the author and maintainer of
the CFF driver.

But I am not really pushing for a refactoring of the Type1 and CFF drivers.
I have a way of solving this problem with very little impact on FreeType,
and I think that's the better way to go.

Graham Asher