ok..already checked the glyphs, but I don’t know where the errors is…maybe too many nodes ?..or the position is mistake ?..sorry for delay respond bhikku..
Figures 3 and 8
Bottom stroke is not horizontal
Semicolon Colon ; :
Contours do not match for height or position. Probably the comma and the semicolon both need to be flipped horizontally, but that is a design choice rather than an error. Look at , in any other font.
Capital J and Q
No overshoot below the baseline
Ampersand @
Does not sit on the baseline or match cap height.
Size of (), [], {}
Usually bigger than Cap height. Again a design choice, rather than an error. Should be symmetrical.
Underscore _
Should be below the line, and match Font Properties, General, Underline size and position.
Lowercase a, b, d, etc.
Compare to lowercase c, which sits on baseline and touches x-height.
Lowercase x
Should overshoot the x-height. Set a guideline for x-height before modifying the x, because the calculated x-height is derived from the lowercase x. Lowercase c, e, g, m, n, p, q, s, etc., align to the guide, not the calculated x-height, while v, w, etc., need to overshoot the guide and align to the calculated x-height.
© and ®
Do not match cap height. Some font designs make them smaller and raised. Again a design decision if you want to go that way.
Trademark 
Align to Cap Height.
cc, ss, ee ligatures
Gap between strokes is too small to be visible at usual sizes like 10 or 12 point. Ligature tt is OK.
£ Stirling
Does not sit on baseline. Bottom stroke is not horizontal.
thanks bhikku pesala..I’ll try to fix it again..
I still don’t understand with this point.
- Should I make a guideline over x-height line and overshoot the lowercase x to touch this guideline ?
- another lowercase like c, e, g, m, n, p, q, s, etc ..should follow this way ?
- “..while v, w, etc., need to overshoot the guide and align to the calculated x-height. ..” I have no idea about this..I really can’t figure it out..
maybe a picture will be great to help me solve this all…thanks bhikku pesala..you are such a good and patient guru for me..
Set guidelines for baseline and x-height for glyphs that do not need any overshoot, like c, e, s, etc. Note that the horizontal strokes of lowercase a should also align to these guidelines.
Select two nodes that are exactly at the same y-position and press shortcut “g” to create a guideline, or double-click the ruler to set guides precisely.
The lowercase x will overshoot both the baseline and the x-height guide.
In font properties, metrics, click on calculate, and FontCreator will calculate the font’s x-height and Cap Height based on lowercase x and uppercase H respectively.
After calculation of the metrics, you have two guides: one for glyphs with overshoot like v, w, x, u, and one for letters like a, c, e, b, d, e, f, g, etc., which do not overshoot the x-height. The purpose of overshoot is to make the tops and bottoms of the glyphs used in text look aligned when the font is used at normal sizes, or when poster sizes are viewed from a distance.
Important Note: x-height = 958 and Cap Height = 1434 are only the default values for a new font. The template is based on my free font Garava.
When designing a font you do not need to limit yourself to these values. Open a few common Windows fonts to see how their proportions and font metrics differ. This is the lowercase from Tahoma Regular. Note how the “n” sits on the baseline, and the left stem reaches the x-height line, but the bowl of the “n” overshoots the x-height, and how the “o” and “s” glyphs overshoot both the x-height and baseline by some distance (about 30 funits).
so with this tahoma font, they have rule that every bowl font should overshoot the caps height and baseline (a, c, e, g, m etc..). I can follow this rule but I can make my own rule, but it should consistent…is that correct bhikku ?
The amount of overshoot that looks right will vary from font to font, so yes, you can make your own rules as long as you apply them consistently. It looks like you may need rather more overshoot than you currently have.
Here is another update version from my font…I hope this is the better one..
please check it bhikku pesala…thanks..
brooklyn suggestions.fcp (43.5 KB)
Look again at !, $, &, *, @, i, j, k, l, m, n, u, {}, (), , © ® and £
ok…
bhikku, did you notice that someone else downloaded my file ?.maybe he want to steal my font when it’s finish..what do you think by that ?
Don’t worry about that. It will just be another forum member who wants to look at it to offer suggestions.
Any font published on the Internet can easily be stolen, but original work is automatically protected by copyright. Protecting one’s rights needs deep pockets and lawyers. A beginner’s font like yours has no commercial value, so why would anyone want to steal it?
OK, I just downloaded from page 1–and I can promise I’ll delete it after I exit the forum.
Your design differs in a few letters than an ITC font (ITC Tetra, circa 2004) which I bought back then for a job. Which is what I would use today for a job if called for.
https://www.myfonts.com/fonts/itc/tetra-itc/
While I’m certain that font designs are stolen everyday, there is nothing that can prevent it. But if you are concerned, the FC projects can be removed from the posts and perhaps you can upload it with each iteration and maybe send BP a private message with a download link if he is willing.
I have deleted the font from my post. I don’t think I can offer much more help on this. It is best for new users to learn by doing rather than having it done for them. That way, one learns more and remembers it better.
thank you for all your help bhikku pesala..sorry for the inconvenience..
in the future maybe I still need a lot of help from you to work with fontcreator. if you don’t mind, of course … if you object, you are still a good teacher to me.
never heard about that font before MikeW, until you gave the link..maybe it’s just the same idea from different people…