Re: [Devel] Problems with Adobe's free CID fonts

[Tom Kacvinsky]

What I meant is that the byte sequence for the callothersubr operator is 12 +
16.  The operands are encoded differently.  So you have a sequence of operand
bytes (one of which is the number 12 or 13, to indicate which othersubr to use),
then an escape byte (12) followed by the byte 16.

Did that make sense?

I have encountered one unknown operator byte: 15.  It isn't in the Type 1
specification.  Terry O'Donnell told me that it basically is a no-op operator.
So perhaps there are undocumented operators for CID fonts.

This is what I am really after: are the problems I am seeing from undocumented
operators, or from a bug in FreeType?

Tom

On Sun, 11 Mar 2001, Werner LEMBERG wrote:

>
> > The invalid subrs index problem is most likely a bug in the code
> > (which I will work on tracking down), but the invalid operator bytes
> > has got me stumped.  As far as I know, the only extensions to Type 1
> > charstrings for CJK fonts that Adobe has made is for counter control
> > hints.  These hints are implemented using OtherSubrs entries 12 and
> > 13.  Which means the byte sequence is 12 + 16.  This doesn't match
> > any of the invalid byte/escape sequences above.
>
> If you can `prove' the byte sequence (12,16), I strongly suggest that
> you contact Ken Lunde directly (at address@hidden).
>
>
>     Werner
>