Font Forum

Wondering when the Bitcoin currency symbol (U+20BF) will be added to the FontCreator's unicode database? It was approved for Unicode 10 June 2017! Currently shows as "Undefined Character". Cheers, Kevin.

Hi, I'm not sure whether this is due to something I am doing (or not doing) but I am having trouble getting the shaping for a Devanagari font to work in Preview and the OpenType Designer. I am absolutely positive that this was working with the same font in previous versions of FontCreator. I can't r...

Such a restriction ie blocking Simple to Mark ligatures would certainly explain why this strange issue is occurring. Using Lookup Type 4 for Simple to Mark and Mark to Mark ligatures is definitely part of the standard methodology for Devanagari script - see Microsoft's doc "Developing OpenType ...

Done! Thanks. regards, Kevin,

Thanks for your offer of assistance. As the project is commercial in nature and still in development I need to request a means of sending the file privately. Please let me know how I can send an attachment privately to you. Regards, Kevin.

Hi, I'm honestly not sure if this is a bug or not because I'm aware that the Font Creator Preview window does not necessarily give a full 100% representation of absolutely all features. I'm working with a Devanagari designed for the Universal Shaping Engine's Indic implementation. One of the lookups...

Thanks for that. Regarding applications that support Descriptive Names, I believe the MacOS Fonts Panel displays these names (in its Typography window). This would automatically provide access to the Descriptive Names to quite a wide variety of Mac applications - eg Sketch, NisusWriter, iBooks, Page...

I'm wondering whether FontCreator is correctly interpreting the syntax for Descriptive Names in Stylistic Set feature scripts introduced as of OpenType specification 1.6. I did a Syntax Check in a font generated from FontLab that had three Stylistic Sets each with a featureName script at the start o...

There is an error in the glyphnames.dat file. "1F57E?whitetouchtonetelephone" should read "1F57E;whitetouchtonetelephone" (semicolon instead of question). Cheers, Kevin.

Thanks for that! I'll update that default glyphnames.dat file using the data in my own customised mapping file that I've been using for years in FontLab. I am curious about the source of the default glyphnames.dat file that FontCreator is using. Does anyone know - I've never seen many of those names...

Hi, I'm new to Font Creator - a refugee from FontLab Studio (although still using it on Mac). I'm intrigued about Font Creator's apparent default Glyph Names protocol. I imported a TTF font generated from Mac FontLab Studio into Font Creator 11 Professional in order to check some OpenType code which...