Font Forum

I am not familiar with how Hindi fonts are designed, but a Standard Ligature glyph substitution should work.

Look at an existing font to see how others do it.

See my tutorial on Adding OpenType Features

Obviously you added the vowels in a different way when editing the fonts that have no code points.

If you use Insert Characters the code-points will be added. If you use Insert Glyphs by name the code-points will also be added. How did you add the extra glyphs?

The glyphs with macrons have no code-points. Open the glyph properties toolbar (F4), select each glyph in turn, and click the icon to generate code-points from glyph names. Then click on Apply to save the changes for that glyph before selecting the next one. If you select the Unmapped category in th...

The font project file would be the most useful. Click on the Attachments tab below the reply box to attach the *.fcp file.

It is up to the user to design the different accents to suit his/her needs.

The script will use the first accent that is available (provided that it is named correctly).

In CompositeData, agrave has three possible accents encoded, gravecomb.case, gravecomb, and gravemod. Many of the existing glyphs use mod accents so these PCAP glyphs need something other. The recommendation now is to use combining accents. Add gravecomb.case to your fonts if you want small or lowe...

I tend to include both forms of germandbls and Germandbls in my fonts so that users can choose whichever they prefer. German Dbls.png The PUA script are largely redundant, but there are still applications out there that do not support OpenType features so the only way to access these extra glyphs is...

That Private Use Area Transform script should probably be deleted. It will only work with earlier versions of CompositeData.xml

The Petite Capital German sharp S was designed for use with other Petite Capitals. It seems that there are two ways to design it.

Substitution and All Caps

There is no problem with your font in FontCreator 11.5 either. I cleared the unused OpenType features in the attached.

Try uninstalling the font, and test the font in FontCreator and some other applications.

Font menu, OpenType Designer (Ctrl F8 shortcut). Click on the Clear button to remove all scripts, though I don't see any there that would affect your lowercase j.

I cannot reproduce the problem here. Both the font test within FontCreator, and a font test in another application display the glyphs as expected. In which application do you see the problem with the j glyph cut off and incorrectly positioned? The only unusual thing I noticed about the font was the ...

Please attach the font project file for us to look at.

1. Show the comparison toolbar (F11)
2. Type the characters you want to use before and after the current glyph
3. Alt+Click on the comparison glyph to go to it. The Before/After glyphs will change to suit.

Go to Font Properties, Metrics, and click on Calculate.

It also fails for me in FC12.

If I open the PDF in PagePlus X9 and do a Preflight test, I get an error:

Box Mismatch: The Trim Box Exceeds the Bleed Box

Exporting the PDF fixes it for FontCreator import.