Recent Posts

Pages: [1] 2 3 ... 10
TypeTool / Re: Kerning not working on some machines
« Last post by Thomas Phinney (FontLab) on Today at 16:27:55 »
The platform shouldn't matter, for any cross-platform font format.

Between that and name changes not taking effect, I wonder if the problem might be related to font caching or the like?

Make sure you have de-installed all other versions of the font before installing a new one.

If that alone does not solve the problem, try clearing all relevant font caches (windows OS, and Adobe-specific if using Adobe apps). See

If clearing font caches does not help, then it is definitely time to contact FontLab tech support, support at fontlab with the usual dot-com extension.
TypeTool / Kerning not working on some machines
« Last post by Jimmy on Today at 08:17:00 »

I recently created my own typeface based on the Freesans default. I've set up kerning pairs which now work on my mac, but when the font is tested on other machines the kerning is ignored. The font was created on a mac and the test machines have been windows based - could this make a difference?

I'm also having a problem getting the font to show up called anything other than Freesans in menus but have tried to set up naming as best I can...not sure what's going on there!

Any ideas?

Cheers all
I think I would just turn off that particular warning in your FontAudit prefs. I believe it is "object is too short" in the English UI.

You can use non-standard em square values, but there are occasional complications, so I recommend saving them for a time when there is a stronger reason. If you need the extra detail, then sure, go to 2000.
What FontLab app are you using to create the fonts and features?
Sorry that it has been a tough road for you! If there are particular topics that could be better covered, we'd love to hear it. Or if you just need a general introduction?

Regarding the particular thing you are talking about, making a connected handwriting font, I just recruited a great type designer and teacher to do a webinar on exactly this topic. It may not be as soon as would be useful to you, but I hope it will help others later!
Actually, what you want to do is perfectly possible. BUT... not in TypeTool. Both of our higher-end font editors, FontLab Studio and Fontographer, have exactly the capability you are looking for.

TypeTool, being a more basic program for a tiny fraction of the cost, does not have all the functionality of those other apps.
FontLab Studio / Re: How to delete glyphs to downsize a font?
« Last post by Sandy JMA on 2014-08-19, 16:40:23 »
I'm not familiar with Chinese fonts, so I can only help generally, not specifically...

It looks like you are deleting characters that are used in OpenType features. After deleting the characters you want to delete, go to the OpenType palette. The top left icon is a drop down menu. Click on "Generate Kern feature". If the glyphs you deleted are not included in any kerning/metrics classes, that will generate a new kerning table, removing any of the glyphs you deleted. Then click on the middle icon at the top of that palette (it looks like a stack with a downward pointing arrow). That will cause FL to try to compile your font. If you don't get an error message, the font has compiled properly and you should be able to generate a font. If you get an error message it won't be quite as generic and should point you to where the problem is.

Hope that helps.
Thanks for your reply Thomas.

I guess it's just a font audit flag and not something that will cause a problem if you decide you want a vector that is 2 or 3 UPMs.

I am actually making a Didot with very refined serifs, so a vector at less than 4 is desirable.

I guess the other approach would be to increase the fonts UPM size, say double it to 2000?

I usually use a UPM of 1000 - are there any issues with using higher UPM size? Say 2000?
This is a minor maintenance release, fixing the problems with installing the FDK under Windows, and running 'ttx'.  Another version, with more fixes, is due in mid-Sept.

On Friday. some people in Europe and Asia would see the updated FDK web page, but the downloaded file was still the previous version. Please  let me know if this is still the case. The FDKReleaseNotes.txt file from the downloaded zip file should show the most recent version as ''build number 63044, Aug 11 2014'.

As several people have noted, the AFDKO macros for FontLab have been dropped from the most recent versions. I dropped the AFDKO scripts for FontLab because the Adobe Type team has not used them for years, and I haven't maintained them for as long. The FontLab scripts that we do use are on GitHub at 'adobe-type-tools/fontlab-scripts. The AFDKO command-line  tools are better alternatives to the two AFDKO FontLabs scripts that we used the most (for auto-hinting and checking outlines). That said,  if any one actually still uses them, I can at least post them on the FDK site as a separate download. Please let me know which ones are still used.
Looking at feature file could help...
send me a PM, I would take a look at your font.
Pages: [1] 2 3 ... 10