1. gaps between glyph boxes, though I snapped the metrics to each box.

that is a metrics problem, you have to kern them together
check for kerning tuts.

2. the “o” still red, even after I closed the contours.

that i dont know... once it writes fine why to bother.. i mean it is your first font.

3. some glyphs need to be typed twice to appear in preview (see image).
some glyphs like “@” show you the glyph you are currently working on, on the preview window, what i want to say is that some letters written in the preview have also a certain function... and you have to write them twice so as they show as a regular preview.

4. in preview the “5” appears instead of the “@”.

it is what i said before. “@” = at so it shows you the glyph you are curently working “at” ;)

IF the “o” was turned red to indicate an open contour when you first generated the font, and you have corrected the problem, you will have to manually change the red indicator by selecting the glyph and choosing “Mark” from the contextual menu (right click or control click on a mac with a one button mouse) and selecting “None” from that menu.

The red indicator can also mean an incorrect Unicode assignment, but that red warning looks different than the one in your example.

Slash and backslash always have to be typed twice, since typing them once is a prelude to other actions in FontLab.

James

thanks guys, I’m gonna fix and update that stuff this evening and if the font turns freeware you are going to get a download link.

BTW, what does a glyph rendered blue
mean in the metrics window of 5.0.3?

hhp

It means it´s part of classbased metrics/kerning.

1. gaps between glyph boxes, though I snapped the metrics to each box.

If you mean the thin line between boxes: No kerning required, better make boxes a little wider than the sidebearings, say 5 units more to each side. In the Metrics Panel you can check that each left & right sidebearing is -5.
It may be that in some apps still a white line appears on screen, but in print it should be ok.

there is more work in that than just fix the metrics of each letter. i think...

Here are some recommendation from Microsoft regarding the thin line between boxes.

“When designing connecting glyphs to avoid pixel dropout caused by rounding, it is necessary to provide for a minimum of a 70 font unit overlap when a 2048 em square (recommended value) is used for TrueType outlines. The amount of 70 units will allow for at least the width of the character to be maintained during the rasterization process at all PPEM sizes.”

ref: http://www.microsoft.com/typography/CursiveScriptGuidelines.mspx

Best regards,
Atif

and now for some more fun with FontLab.

in Illustrator the glyph boxes are of equal size 90x140 (see the transform palette, first image) but after importing in FontLab the “g” is smaller than the “n”. thus after importing the “n” fits to the metrics - the “g” failed.

what happened and how to solve this problem?

here are the “n” and the “g” for download:

http://www.megaupload.com/?d=E97956RM
http://www.megaupload.com/?d=JAI8FQQN

ghurman,

if you think this is a problem, I suggest:

http://www.fontlab.com/support/problem/

Please attach all relevant files (Illustrator, VFB) in one .zip file.

Adam

Make a new font in FL.
Digitize the x and y bounds of the whole em in the font’s “n” glyph.
Generate a font and compose that n in illustrator.
Scale the Em to the size you want it in Illustrator.
Draw or place each glyph Staying Inside the lines.
Import glyph and em.
Delete Em.

Hope is, this helps.

Cheers!

Try pasting instead of importing, that´d work.