Font Forum

I've found a few things in glyphnames.dat that might be issues and might be worth fixing. I'm using FCP 11.5.0.2430, and the date on my glyphnames.dat is 8/3/2017. Here's what I've found: *** The entry: 21B5;carriagereturn should maybe be something like: 21B5;arrowdowncornerleft *** AFAIK, These ent...

I too have see no problems with exported fonts ... and the work-around you suggested is AOK. The only problem would be if data points exceed the +/- 32K limit, which is really extreme. I'm thinking this is definitely a low-priority issue , and not worth risking the issues that might crop up from exp...

Thanks for that! ... I never thought of transform / moving the contours into "safe space" and then sliding them back ... btw, it looks like, as long as the contours are within -32,768 to +32,767, the exported font is AOK. Scaling and rotation of component glyphs is know to cause issue, so...

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 ... S...

I seem to be hitting some issues in FC Pro 11.5.0.2430 on Win7x64 with fonts that have very large glyphs. It appears that coordinate points of a glyph are bounded by -32,768 to +32,767 (I can't find this in the OTSpec, and I've asked this question in the FontCreator - Support forum under the title M...

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...

It's the theme! Didn't think of that ...

Yes, Grid Options is similarly crippled. I can't change themes at the moment on my system to absolutely confirm this, but I'm sure you've got the right take on this issue ...

Thanks for the support!

Thanks for that! I kind of figured that the issue is rare (or just me) ... but I wanted to mention it in any case.

Could be my graphics card, could be Win 7 (soon to be orphaned in Jan '20), could be gremlins!

Kind of a niggly, but mildly annoying ... My Metrics Options window looks like this: FCP11_5_MetricsOptionsA.jpg I deal with it by clicking the topmost checkbox, which then gives me this, which is an OK workaround: FCP11_5_MetricsOptionsB.jpg FontCreator Professional Edition 11.5.0.2430, Win 7 x64, ...

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, xCoordinate...

Thanks Erwin! In the flock of specs, recommendations, and documentation available, it is daunting to figure out what is current and correct vs. info that is deprecated, superseded, or just plain wrong. I'm running multiple pipelines on development and can keep a parallel line of a few fonts that car...

I am using FCPro 11.5.0.2430 (64-bit) on Win7x64. I realize that the FontCreator 11.5 manual Page 41 (p48 in the PDF) indicates that these are "obsolete glyphs". However, the OpenType spec 1.8.3 does call for .null at least - see the specs for the COLR table: Fonts using COLR and CPAL tab...

I'm hoping to someone can point me to the specification or rationale for how FCP maps glyphs in a new font file. I am exporting my font with 'cmap' tables for platforms 0-2 (Unicode/Uni 2.0BMP, Mac/Roman, and Windows/UniBMP). The first four glyphs are .notdef , .null , nonmarkingreturn , and space ,...

The FCP 11.5 manual, p184 says ... From the Tools menu you go to Options and go to the Samples page. Here you can select the font filename to be used in the Samples toolbar. ... but this now lives at the bottom of Tools => Options => General tab (I poked around for "a while" to find it ...).

Thanks Erwin!