Hi, I have FC15 proffesional edition, until yesterday I worked on a font that always I could test it (by: Test Desktop Font (ttf/otf) / F5), but since yesterday it shows me the text written in Ariel rather than the current font that I’m working on.
Would you like to explain me what to do in order to be able to make this font test function availble again?
Most likely something in the font was accidentally changed or damaged, so Windows can no longer use it correctly for the temporary desktop font test. When that happens, FontCreator may fall back to another font, such as Arial.
It is hard to know exactly what is wrong without seeing the font and the FontCreator project file.
Please send both the font file and the FontCreator project file to us at:
We will take a look and let you know what needs to be fixed.
I appreciate it. Thanks.
Thank you for sending the font.
I tested the Font Test dialog here with your font in both FontCreator 15 and FontCreator 16, and it works correctly. So at this point I do not see anything wrong with the font itself.
Could you please check whether the same problem happens with other fonts as well?
It might also be a temporary Windows/font-cache issue, so please try restarting your computer and then test the font again.
As a workaround, you can also use Font → Test Web Font, which should allow you to preview the font in your browser.
Thank you for your assitance.
When checking the English Font, indeed, it works, but the problem isn’t with English font. May I ask if you checked the English font only?
Beside that, I closed all my open docs and programs rebooted my PC before I came here to write my post and tried to take advice from Gemini. Unfortunately all Gemini advices regarding that, including the PC rebooting, were unsuccessful.
Thank you for the additional information you sent by email. That made me take a closer look, and I now understand the issue.
Your font does contain Hebrew glyphs, but those glyphs no longer have Unicode code points assigned to them. I am not sure how that happened, but without code points the Hebrew characters no longer exist as usable characters in the font. As a result, Windows falls back to another font, such as Arial.
To fix this, you need to assign the correct code points back to the Hebrew glyphs.
You can do this manually by selecting each Hebrew glyph and clicking Auto Fix next to the Code-points edit field. Alternatively, if you have an older working version of the font, you can use Copy and then Paste Special, selecting only Code-points, to restore them.