Re: CID + CFF drivers available

[Tom Kacvinsky]

One of the things that can be confusing about CFF fonts is that the
index arrays might consist of 1 byte offsets, ot 2 byte offsets, or 3
byte offsets, etc... If the offsets are off, the what is passed to
T2_Parser_Run might not be the correct location of the dictionary to
be decoded.  I can't remember which part of the index data structure
(here, I am talking about the structure as defined in the CFF spec)
tells us what the offset size is supposed to be.

Tom

On Fri, 2 Jun 2000, Werner LEMBERG wrote:

> 
> > I can't seem to get *any* OpenType/CFF font to work with ftview.
> > This includes the CFF fonts that come with Acrobat 4.0, and the
> > OpenType/CFF fonts available to me via Adobe's OTF beta program.
> 
> > Unfortunately, I don't know why this is the case; is there a way of
> > tracing what happens when a font is opened?
> 
> Define the two DEBUG macros in include/freetype/config/ftoption.h!
> 
> In case of CFF fonts you will get the error message
> 
>   T2.New_CFF_Font: no charstrings offset
> 
> As mentioned in another mail, T2_Parser_Run() doesn't get any
> reasonable results (and I don't know enough about CFFs yet to give
> more hints about the reason).
> 
> 
>     Werner
>