Font Forum

Last week I stole a two years old car. After a week the owner took it back.

So I tried to steal it again, but the owner change the lock.

Now what should I do?

I need to know a little more about the way you work with kerning pairs, but I first want to make clear it is not allowed to have duplicates in a single sub table. If you work with class based kerning you can use exceptions but that is a different topic. Before you start worrying, on export the dupli...

Does it work after a reboot?

I'm looking into this, but it takes time. I hope to find a solution within the next couple of days.

Maybe other ranges are conflicting; for example if "Greek and Coptic" is selected as well then the Arabic sample text is not shown.

Word will always show one style per font family. If the regular version exists, it will be shown. Arabic fonts created with FontCreator should automatically show the comment / sample text. But you can always manually force FontCreator to setup your font for the Arabic comment in Word: To have the Ar...

Did you install and run MainType version 6?

I don't think those OpenType layout features are causing the problem, but if you suspect it, why don't you export the font without OpenType layout features and try if that works?

So many things can be the problem, so it might be better if you provide more information, or send us the font(s).

dmills wrote:Do I need to change a setting to have this value included in my font export?

No. It is included, but it seems your software/tools fail to reveal it.

In the OS/2 table. Here you go:

http://www.microsoft.com/typography/otspec/os2.htm#ch

You could also consider making a specific keyboard layout. I guess that has some benefits, but it depends on your exact needs.

The space character contains incorrect codepoints: $00, $08, $09, $0D, $1D It should only contain $20. You can simply replace them through the glyph properties tool window. The fastest way is to just click the "Auto complete code points based on glyph name" button. Don't forget to also cli...

I see. You removed the first couple of glyphs, and especially the first (.notdef) is extremely important. I urge you to put it back (just insetrt a glyph at the top and provide a meaningful outline) and see if that solves the problem.

I don't think Word 2013 supports color fonts. The color font technology is adopted very slowly.

I don't have time to investigate the font, but I suspect this is happening: Word auto-magically replaces plain quote characters with smart quotes, which are not included in your font. And while Word tries to be smart, it then decides to use a fallback font :? You can add "left and right single ...