Font Forum

Built-in font, Trado.ttf is correctly implemented and tested flawlessly in FontCreator. But when other Windows applications implement it, they do a tiny incorrect different thing than the FontCreator.
It is a connection of lam ( ل ) followed by aleef ( ا ), on applications it seem to be not complying the ligature script so the glyph shape of ل is just concatenated with ا. For distinctive explanation just look straight at fact:
فَلَا تَكُ فِي مِرْيَةٍ مِمَّا يَعْبُدُ هَؤُلَاءِ مَا يَعْبُدُونَ إِلَّا
^ ^ ^
not correctly shown in Editpad, Notepad++, Maktabah Shamila.. or may others

How to solve this troublesome application incorrectness ?
Many Thanks in advance

Many applications don't support Open Type features.

A word processor 'should' display it correctly, Microsoft Word probably will and so will Libre Office. Also Desktop Publishing applications like Page Plus will probably work OK.

However text editors like Notepad++ and Editpad don't usually have Open Type support so things like ligatures will not be displayed.

Is the original font working correctly?

And is it failing after editing with FontCreator?

The MS system fonts which contain Arabic glyphs have errors with Arabic typing like rendering or SHAPING, DICRITICTS COLLISION with letters and insufficient coverage of full repertiore.