From: John H. Jenkins (jenkins@apple.com)
Date: Mon Nov 13 2006 - 17:49:37 CST
On Nov 13, 2006, at 4:41 PM, James Kass wrote:
> Would ".notdef.5055675" meet the specification for one of these
> glyphs,
> for instance? Or would this mean that other OS validators would then
> fail to pass the font?
>
Probably, since ".notdef" is supposed to be the only name that starts
with a period. Apple also allows ".null".
Personally, if I *must* give a glyph a nonsense name, I tend to go
with "gidDDDDD".
> If there are no inaccuracies in my (and many other developers') post
> tables, does Apple recommend that we correct certain accuracies?
>
No, Apple recommends that you file a bug against our software. If the
font works OK on Windows, it should work OK on a Mac.
FWIW, the validation engine in the Tiger version of Font Book has not
proven particularly satisfactory and we are hoping to introduce
improvements in future OS releases. My recommendation to a font
vendor who finds their font doesn't pass muster with Font Book when it
does work on Mac OS X (or even Windows) would be to file a bug.
========
John H. Jenkins
jenkins@apple.com
jhjenkins@mac.com
http://homepage.mac.com/jhjenkins/
This archive was generated by hypermail 2.1.5 : Mon Nov 13 2006 - 17:50:56 CST