Re: [Fontforge-devel] FontForge & CIDFont resources

[Ken L. <lu...@ad...>]

George,

I am very glad to hear that you figured out the cause of the problem,  
and more importantly that it is now fixed. I wish I had been able to  
send to you the font that exhibited the issue.

Type 1 CIDFont resources continue to be important, not for delivering  
fonts to customers, but as one of the source files for building  
OpenType fonts.

About the OpenType Beta Program, I know all too well what it is like  
to have far too many irons in the fire. If you know of anyone who you  
think would benefit from participating, please let me know.

With best regards...

-- Ken

On 2009/02/23, at 8:06, George Williams wrote:

> On Thu, 2009-02-12 at 10:58, Ken Lunde wrote:
>> The specific problem that I encountered was that the CIDFont resource
>> was missing CID+0, which is equivalent to the ".notdef" glyph in Type
>> 1 fonts. Of the 64K glyphs that can be in a CIDFont resource, the  
>> only
>> one that is actually required is CID+0.
> Ah. I finally figured out what the problem was... And it is still
> present in the current version. It is now fixed in the cvs tree.
>
> When generating Type1 CID font resources (but not CFF CID), and the  
> font
> contained a ".notdef" glyph, then FontForge would not output that  
> glyph.
> If the font did not contain a ".notdef" then FontForge would output a
> ".notdef" glyph. Totally backwards behavior.
>
> This bug was probably introduced in the release of 14-Oct-2006 and has
> (probably) been present ever since.
>
> On Fri, 2009-02-13 at 14:04, Ken Lunde wrote:
>> I am not sure what the significance is of the date-like digit string
> It is the date of the release (or the date the sources stabilized, the
> release might be the next day or so).
>
>
>> Unfortunately, without an NDA in place, I cannot pass the font to  
>> you.
>> But, if you were to be added to our OpenType Beta Program, I could
>> pass the font to you through that mechanism.
> I don't think the bug exists in OpenType fonts though. I was only able
> to reproduce it in Type1 CID Resources. Similar tests worked for CFF  
> CID
> Resources. Which may be why no one has noticed it before.
>> (And, I would think that
>> you'd want to be part of the OpenType Beta Program anyway. If you  
>> like
>> this idea, please let me know what email address to use.
> Had I but world enough, and time...
>
> I'm afraid I no longer have the time and energy to pursue this. I've  
> had
> to cut back on the time I spend on FontForge recently (and there  
> really
> isn't anyone else).
>