All articles 56

Hi all,

I'm designing a handwriten font wich contain many alternate sets of characters and I programmed a calt feature to randomize it. The feature contains a lot of lines mixing and conditioning the substition of each character. I thing the sintaxis is fine and the replacement works fine too, but when I increase the number of characters in each of the classes used in the code the output panel shows the following warning:

[FATAL] GSUB feature 'ÿÿÿÿ' causes overflow of offset to a subtable (0x1140a)

(I don't know why the name of the feature is swhown without the correct name).
I guess it means the code becomes too heavy but searching and reading a lot of posts of similar bugs I concluded that the responsible of this issue was the program. So I decided to try compiling the font in an older version (FL 5.0) and there aren't any problem and the compiled font works fine.
Please tell me what can I do to improve my version of FL to avoid this issue. Any comment will be appreciated.

I'm currently working on a font and I've found an issue which baffles me, shown here: As you can see there are these out of place lines over the "u" and "y" glyphs, and they're not the only affected glyphs. The issue crops up in Photoshop when the font is displayed at small sizes or has anti-aliasing off. What's weird is that the lines don't actually exist on the vectors, FontLab renders them appropriately and there's nothing suspect on the offending glyphs which sets them appart from the others that render properly.

Help would be much appreciated.


Indices: Tools: Type Design Tools : TypeTool

TypeTool is a basic font editor for Mac OS and for Windows. For students, hobby typographers and creative professionals who occasionally need to create or customize fonts.

TypeTool 3 released in March 2007 includes support for OpenType fonts with up to 65,000 glyphs, Unicode 5.0 support, new bitmap Background and outline Mask layers, improved Bézier drawing with open contours and tangent points, multi-line metrics and kerning editing, and screen quality autohinting.


I have a problem in drawing in fontlab, always my letters are not smooth when I display it on screen. So, what is right way or best way to draw in fontlab? any help please?


I keep changing things within the kerning and whenever I generate a font, it asks me if I want to rebuild the kern feature.

Sometimes, I get the dialog box when generating the OTF font file at the end of the exporting process... and that's when it freezes the program. the only safe way I can rebuild it is to rebuild it within the opentype window and then generate the font.

I'm afraid i'm damaging the font?

Any suggestions would be greatly appreciated


I'm new on the forum so I introduce myself

i'm a swiss student, and I tried for my studies In ancient history to build a font.
I used fontforge and finally fontlab. Everything works perfectly except the kerning.

MS word 2010 doesen't take count of the kerning of my new font...
Kerning works perfectly on Oppen office, but I have to make it work on MS word. Is it possible ?

Somebody knows what is the problem ? Can somebody help me ?

Thanks for help :)

Hey Guys...

I have a big problem and I know there are a bunch of smart font people on here so I sure you can help...

I'm building an icon font in FontLab Studio 5.1 and for the life of me I cannot get the font to show up in Microsoft Applications (Word, Powerpoint etc.). Shows up in every other professional app like Illustrator, InDesign... I read all the docs on Microsofts website pertaining to output when making a typeface by MS standards and I followed it perfectly (I think).


I'm hoping someone can lead me in the right direction...

Thanks a ton in advance :)

Hello to all!

I've just went live with a simple tool to generate encoding text for FontLab.

It's still in a very early stage (I'm sorry if it's still too painful), but I want to share it with you guys in order to have feedback/suggestions.

Here's the link:


[FATAL] cmap{plat=3,script=1,lang=0}: multiple glyphs uni2126 Omega mapped to code <2126> ERROR: There was a problem while compiling OpenType font. Final .otf font is not saved. Please, check OpenType features definition for errors

Once more I am confronted with an error in FontLab, which I don’t entirely understand. Especially the help suggestion is entirely useless. I understand the issue is caused by “multiple glyphs” with the unicode 2126, but how do I find, identify and eliminate the duplicate entry if it isn’t showing up in the glyphs list? How do I know which is the right associated character, which is the original and which the duplicate?

I love some features of FontLab, but its approach and mysterious ways are really frustrating sometimes. It shows that this software is quite old, compared to modern applications. Glyphs, a relatively new app, shows promise, but I can’t justify to dash out another $329. Designing fonts is a passion of mine and I understand virtually no one can live from it (except maybe H&FJ and a few others)…

If you know a solution to my second FontLab error I cannot fix alone, please let me know.

Here is the message FontLab gives me:

>>>[FATAL] aborting because of errors:
syntax error at "-63"
[/Users/chrisL/Library/Application Support/FontLab/Studio 5/Features/fontlab.fea 11]

I had been cleaning up classes and getting rid of some duplicate commaaccent glyphs when I tried to recompile. The message above is what happened.
I then made a copy of the file and one-by-one deleted each feature and attempted to recompile between each removal to no avail. It seems as though it may be something in the classes but I am going nuts for 2 days now trying to find it!

I am hoping someone can clue me in on my malfunction.

Desperately seeking help,


Hi! I'm designing a layered typeface with three weights and some extra glyphs (ligatures, swashes and some weird alternates). I made open type feature for ligatures and kerns but I let some extra glyphs without feature. When I use those glyphs and I change the weight, the glyph doesn't change. For example, if I write "BARCELONA" with one of my extra B's, and I change the weight, it change all the word except the B.
I've been looking the generated file and it seems that those extra glyphs without feature doesn't have UICODE names, so when we change the weight, they doesn't change. I've tryied to use the option GLYPHS>GLYPHS NAME>GENERATE UNICODE but it doesn't work.
Anyone knows what can I do to generate the same UNICODE names on the three weights.
Thanks for your help and sorry for my english!

In the last issue of the digital inDesign Magazine FontLab states: Fontographer for Mac and Windows is coming soon.

Hello Forum,

I am stuck at one point in FontLab and hope someone can help me.
I would like to integrate arrows in a TrueType font using FontLab: arrow right and arrow left.
The font should be used as a webfont later and i don´t want to build in images for arrows anymore.

To achieve this I proceeded as follows in FontLab:
- Create a Glyph in an empty grey box wich is marked yellow in the font-window
I understand that glyphs, that are not yellow do not belong to the currently selected encoding, codepage or Unicode range
- then i rename the glypgh-name to "arrowright" (using the context-Menue) and generate the unicode index for it (2192) using the little diamond
- After that action the Glyph is marked as grey (unencoded?) and it goes to the end-section in the font-window.
The arrow does not appear in the exported font. I tried TrueType and OpenType.
The font consist of 234 glyphs.

Do you have any ideas, what i am doing wrong?
Does the unicode codepage not support arrows?
I would be grateful for any hint.


Edit-Find or Command-F can help me find glyphs in the font window, but what's the easiest way to track a given glyph down in (a) my classes, and (b) my OpenType code, within Fontlab?

Hello everyone,
I've a question about horizontal and vertical stems in FontLab.
Going to Font Info --> Hinting Settings --> Standard stems (T1 hinting) it is possible to define values for horizontal and vertical font's standard stems.
But when I'm in a blank Glyph Window is there a way to visualize horizontal and vertical hints based on those values?
I mean, how can I make those values useful for the designing process of the glyphs?
Thank you for your help!


I have a problem with my font which has been stopped typing numbers! when you for examples write 1 it's type something else which other glyph I used that has not unicode ,, and the same problem form other numbers..

I have delete some unnecessarily glyphs before, so is it the problem? maybe the index has been changed? or it is a problem in the programming? anyone knows please?



I did something unintentionally, while I was sorting my glyphs, anyway - my tools are all grey/translucent now and I can't change a single thing. "erase tool" is grey, "knife tool" is grey, "elipse" - everything. I basically can't select any of the tools, nor a single dot when I open glyph window and I don't know how to undo what I just did. I quit and restart, but the problem remains.
I attached a snapshot.

Thank you for your help!

| Attachment | Size | | --- | --- | | snap_fontlab_disfunctional.jpg | 68.7 KB |

Hello guys!

I've been desiging a Font in Hebrew, But I can't seem to find how to generate a Hebrew font in FontLab.

Let's say I've got all I need already, and I have FontLab. How do I create a Font in Hebrew? is there a Code Page for Hebew? How do I "turn it on"?

I'm very new in the typograhpy field, so every little detail is needed and will help me.


I am working on a typeface and I notice these small red rectangles below several glyphs in FontLab.

Can anyone tell me what this indicates? See attached image below.



| Attachment | Size | | --- | --- | | red dots.JPG | 13.3 KB |

I recently completed a failed font experiment, and, although I don't know if it's of any interest to anyone, I thought I'd share it anyway. If my wasted time fuels someone else's creative endeavors, then it wasn't entirely wasted.

The concept was weighting glyphs in a font based on their frequency of use in a given text canon. So, for example, my plan was to have a Shakespeare version of the font, a Brontë version of the font, etc. The less frequently a character is used in the canon, the darker the character would be in the font.

In any case, a more detailed writeup that includes python scripts and examples can be read here.

Updated uranges.dat file for FontLab.

All Unicode 7.0 Character Ranges, plus Control Codes, ASCII and Latin-1, with the ranges sorted in alphabetical order for ease of use.
Rename from uranges.txt to uranges.dat and place in
~Library/Application Support/FontLab/Data/
(OS X)
This location can also be defined in the FontLab preferences window.
See documentation for Windows location of this file.

| Attachment | Size | | --- | --- | | uranges.txt | 8.5 KB |

First, I’m kind of new to this.
I’m about to create a Script font and I have some problems with the lower “r” and the other lower glyphs connected to it.

Am I supposed to do a ligature for every lower letter connected to the lower “r”? That sounds weird.
When I look at my script fonts installed on my computer there are no big amount of ligatures.

There must be some other solution to it.
When I look at fonts on MyFonts, like Ciao Bella, there are no ligatures for the lower r but when I write it in the “Sample text” field there is a more accurate connection between the lower “o” and the lower “r” and the “e” and the “r” and so on.

Any smart and simple solution to this?
Please help me.

Thank you.

hello. i wondered if anyone could provide any help or advice with fontlab? at the moment it seems to have set a default descender of -250pt. the typeface i've created drops below this and when i test/generate the font all the descending glyphs are clipped slightly where the tails exceed the descender line.

i imagined dragging the descender below the lowest point would have solved the problem but it didn't seem to affect it. perhaps there is another way?

any help would be greatly appreciated.

FontLab is surveying users of their software (and competitors), and offering some nice prizes for responses, and even just tweeting about it.


There is a new group for shearing Scripts & Macros on facebook:

Feel free to join and share!