I am happy to create a test font of simple shapes to see which shapes/curves/points are the ones that get shredded. Such a font would show clearer what outlines cause issues with the Apple engine and would be simpler to debug.
On 27 Oct 2011, at 20:44, Werner LEMBERG wrote:
Urgh. With FreeType, I get exactly the same result as before, and
FontValidator gives no error messages any more with the bytecode. I
haven't tested yet whether MS gives the same results...
Sigh. I'll now check the documentation of all involved instructions,
but this time in the Apple one. Maybe they differ in some subtle way
which I'm not aware of...
Thanks for testing! Any other ideas how to proceed? Hopefully, I
don't have to prepare a suite of test glyphs to check all involved