[Devel] Re: CFF problems

[Tom Kacvinsky]

I figured out what was going on:  upon entering parse_t2_real, the byte stream
is pointing at the inital 0x1E.  Thus, the advancement of p gets use past that
and into the real data.  Now I understand why this works...

Attached is patch -- please review this...

Tom

> 
> 2. I found some errors in the function parse_t2_real, which is in t2parse.c
> I won't commit this; I want other eyes to see it first.  The "fixes" I made
> work, but I had to do some things I didn't understand.  For instance, the byte
> stream seems to start at "start + 1" instead of "start".  So I incremented the
> byte stream pointer to get around this.  Why?  I'll send the patch later after
> I do some more grubbing around.
>

t2parse.diff
Description: Text document