It looks like FC limits the size of a glyph to the (symmetrical) range -16,383 to +16,383 (from zooming out and in on a design window). Is there a reason for this that I am missing?
The OPSpec 1.8.3 declares these points as int16 (I'm looking at the glyph table, Simple Glyph Description, xCoordinates[] array). This would seem to imply an (asymmetrical) range of -32,768 to +32,767.
Max Size of a Glyph
Re: Max Size of a Glyph
Wouldn't an asymmetrical range throw everything out of balance? I guess not.
I think compound bows are my favorite to hunt with.
Re: Max Size of a Glyph
I think the "asymmetrical" comes from two's complement math, which generally can represent one more negative number than positive number for a given number of bits.
My core question is:
For an [X,Y] point in a glyph, what is the allowed range for X and Y?
I'm really just trying to find the answer to this question. I'm wondering if FC is limiting the range to -16,383 to +16,383 because the OpenType spec limits the range, or for some other reason.
The int16 data type would seem to imply a range of -32,768 to +32,767 ...
-Clint
My core question is:
For an [X,Y] point in a glyph, what is the allowed range for X and Y?
I'm really just trying to find the answer to this question. I'm wondering if FC is limiting the range to -16,383 to +16,383 because the OpenType spec limits the range, or for some other reason.
The int16 data type would seem to imply a range of -32,768 to +32,767 ...
-Clint
Re: Max Size of a Glyph
Looks like there are bona fide Arabic fonts with coordinates well past the 16K bounds, and FCP seems to handle them fairly well (although there is no working grid beyond 16K, and you can't zoom in to do detailed work, but the fonts are exported OK). However, there are other issues in this area ...
See the post in the FontCreator - Bug Reports forum with the title Glyph Coordinate Bounds.
-Clint
See the post in the FontCreator - Bug Reports forum with the title Glyph Coordinate Bounds.
-Clint