New version of AFDKO is available

Primary tabs

7 posts / 0 new
Last post
Dr. Ken Lunde's picture
Offline
Joined: 17 Sep 2006 - 8:31pm
New version of AFDKO is available
0

For those who use AFDKO tools in their font development workflow, please take note that a [[http://blogs.adobe.com/typblography/2012/09/new-afdko-version.html|new version]] was released earlier this month.

Dave Rowland Schizotype Fonts's picture
Joined: 19 May 2009 - 6:33pm
0

I'm getting the following message trying the new autohint tool:

Autohinting starting for font GibLI4.vfb Sun Sep 09 15:48:56 2012
Hinting C.
Skipping glyph C. Failure in processing outline data
Hinting F.
Skipping glyph F. Failure in processing outline data
Hinting E.
Skipping glyph E. Failure in processing outline data
Hinting B.
Skipping glyph B. Failure in processing outline data
Hinting G.
Skipping glyph G. Failure in processing outline data

I get the same message on any font, not just mine. I've just upgraded from AFDKO 2.0, and I'm wondering if I've done something wrong. The old Autohint macro was still in the macros folder and now that doesn't work either. I've deleted all the old macros and reinstalled just the new ones but still getting the same message. Anyone else struggling?

Read Roberts's picture
Offline
Joined: 17 Sep 2006 - 12:12am
0

I see that you have installed the new FDK scripts for FontLab macro's, and I assume that you also updated the shared script files under Macros/System/Modules - in any case, if you used the script 'FDK/Tools/FontLab/installFontLabMacros.py' the installation will be correct. In this case, I do not know of a reason to have the problem you report. Would you be willing to post your vfb file for me to look at? You could perhaps make a small subset font to make it easier to send. If so, send me a zip file at rroberts@adobe.com. Please rename the extension to 'adobe' - that helps avoid problems with the firewall.

Also, what version of Python of FontLab, and which OS ( Mac or Windows) are you using?

- Thanks, Read

Dave Rowland Schizotype Fonts's picture
Joined: 19 May 2009 - 6:33pm
0

Hi Read,
I don't think it is a problem with the vfb file, as I've tried it on other fonts (including Adobe Source Sans) and had the same results. I thought there might have been a problem with the way I installed the FDK folder. Initially I just deleted the old one and pasted in the new one then ran the installFontLabMacros.py script to save the macros into [C:\Users\DavidRowland\Documents\FontLab\Studio5\Macros]. I've tried again by restoring the old FDK folder and pasting the new one into the same place to merge the two (I also deleted all AFDKO files from the [C:\Users\DavidRowland\Documents\FontLab\Studio5\Macros] folder. I then ran the installFontLabMacros.py script again and started Fontlab. The old autohint script (in outlines folder) now works again, but the new one (hinting folder) still gives the Hinting F. Skipping glyph F. Failure in processing outline data message.
I'm running Fontlab 5.0.4 with Python 2.4 on Windows 7 PC.
I also tried running the FinishInstallWindows.cmd script in case that was part of the problem, and got the following message:

My account type is administrator so I'm at a loss as to why this would be the case. Even so, I tried the Type "autohint -h" (no quotes) and hit "Return". This should give you the Help information about the Autohint tool. step from the installation instructions. I got the autohint help but also this message flashed up:

Does any of this information help at all?
At least I have the old FDK working again, so if you can't solve the problem, please don't worry about it.
Cheers,
Dave

Read Roberts's picture
Offline
Joined: 17 Sep 2006 - 12:12am
0

I can't be sure that missing the 'MSVCR100.dll' is the only problem, but it is a sufficient problem. The issue is that the FDK is compiled with an older version of the Microsoft compiler tools, in order to be compatible with Windows XP. Windows 7 no longer includes this library. I thought I had solved this, by compiling this library into the autohint program, but this is obviously not the case. You can work around this by downloading the file, and copying it to:
C:/Windows/system32/

You can just google "MSVCR100.dll download"
but it can certainly be downloaded from:
http://www.microsoft.com/en-us/download/details.aspx?id=5555
Please download and install this file, and then let me know if you still have a problem

Dave Rowland Schizotype Fonts's picture
Joined: 19 May 2009 - 6:33pm
0

That's solved the problem! Thanks very much for your help.

Dr. Ken Lunde's picture
Offline
Joined: 17 Sep 2006 - 8:31pm
0

Many thanks, Read. And, thank you, Dave, for reporting this issue, and following up with the details that Read needed.