Unicode characters exception. (TypeError: Cannot read property '0' of undefined) about opentype.js HOT 5 CLOSED

This version specifies that no PostScript name information is provided for the glyphs in this font file.

cf http://www.microsoft.com/typography/otspec/post.htm

I am getting the same error with Arial Unicode MS regular (ARIALUNI.TTF).
Would using the gh-pages one be a real downgrade?

The error seems to be that you don't handle version 3 there: https://github.com/nodebox/opentype.js/blob/a43a85ddccdc3560086b269a291cae1ed5ef8f51/src/tables/post.js#L24

Temporary fix: } else if (font.tables.post.version !== 3) { line 216

While you are it you could add version 4 as well.

from opentype.js.

@darionco sorry for the late reply. I'll look into it tomorrow. The gh-pages version is an older version and will be upgraded soon. I'll also fix any performance regressions in master. I've had to undo some performance optimizations to enable font writing.

@Mouvedia support for post version 3 seems like a good idea. While looking into format 4, the Apple site you mentioned states:

As a rule, format 4 'post' tables are no longer necessary and should be avoided.

So not really sure if it's worth it. Do you have fonts that require it? Could you send me one for testing?

from opentype.js.

Do you have fonts that require it?

Not yet.
Support for version 3 is essential I agree.

from opentype.js.

The performance you see for big fonts is because we add the Unicode code point and glyph name to each glyph. For large fonts, this causes some overhead.

In special cases, we could disable this post-processing step to speed up parsing when you don't need all the data in the glyph. Does this sound useful @darionco ?

from opentype.js.

@fdb Absolutely, although we do use some of the glyph data to layout the text, so an option to only parse metrics maybe? would that be sensible? if not, I believe the current performance is something we can work around.

from opentype.js.