On Wed, Mar 28, 2012 at 04:12:58PM +0200, Khaled Hosny wrote: > On Wed, Mar 28, 2012 at 09:54:52AM +0200, Patrick Gundlach wrote: > > Hello Khaled, > > > > can you tell me what you did (postprocessing) or how the fontforge bug > > can be circumvented? > > I use FontTools Python library to open the fonts after FontForge > generates them and set the respective fields in OS/2 table directly, see > for example: > http://crimsontext.svn.sourceforge.net/viewvc/crimsontext/trunk/tools/generate.py?r1=96&r2=95&pathrev=96
The issue is now fixed in FontForge's GIT master, so fonts built with it should be OK now. Regards, Khaled
