Forum Replies Created
-
Posts
-
ah typo bug, thanks for posting
a temporarily workaround could be could be
g = CurrentGlyph() ## create a copy layer and copy the glyph to that layer gCopy = g.copyToLayer("copyLayer") print g, gCopy #to show these are not None print gCopy.getParent() g.removeOverlap() # works okay gCopy.removeOverlap()(edited your post a bit)
I will turn autohint off when there are no blue values given in the font info in the next version, this will solve the mystery :)
It will be displayed in the generate sheet as disabled if a font has no blue values
yeah, I noticed this issue to.
But it not always failing.I would advice to set blueValues if you enable autohint to generate binaries.
see the FDK doc and tutorial:
1.5 Using autohint
After the mergeFonts and rotateFont tools are used to generate a CIDFont, there is another very useful tool that can be used, available in AFDKO Version 2.0 or higher, called autohint. The autohint tool can be run on name- and CID-keyed fonts, and uses the hinting parameters—BlueValues array, OtherBlues array, StemSnapH array, StemSnapV array, StdHW, and StdVW—to apply hinting to the CharStrings. You are encouraged to explore its command- line options to determine which are the most appropriate to use.
1.5.1 Calculating Alignment Zones & Stem Width Values
You are strongly encouraged to take great care in calculating the alignment zones and stem width values. The stemHist tool, also included in AFDKO Version 2.0 or higher, is designed to help in calculating alignment zones and stem width values by generating histogram data. The former functionality is invoked using the “-a” command-line option.
that is a really bug :)
a workaround:
from fontTools.misc.transform import Transform f = CurrentFont() t = Transform().scale(.5, .5) ## possible transformations: ## .translate(x, y) ## .rotate(radiansAngle) ## .skew(x, y) ## .inverse() for g in f: g.transform(t, doComponents=False) # or for each contour # for c in g: # c.transform(t)hope this helps,
thanks for reporting and this will be solved in the next update.yeah off course, you scale the component base glyphs to :)
so components will be double scaled, once by their base glyphs and once by the component transformation that get scaled.ooh sorry to fast :)
only in multiple window mode off coursethis is fixed, it will now be possible to use nested components and get proper updated views. The major drawback is that the user is responsible for not having loops of components….
be careful :)yeah only in single window mode press alt+Space Center toolbar icon
RoboFont uses ufo2fdk to build the otf files.
FDK requires a FontMenuNameDB (see MakeOTFUserGuide.pdf page 6-10)
ufo2fdk builds a FontMenuNameDB with the following font.info values:==== ===
[PS] postscriptFontName
f= openTypeNamePreferredFamilyName
s= openTypeNamePreferredSubfamilyName
l= styleMapFamilyName
m=1, openTypeNameCompatibleFullName
==== ===If you use accents or none ascii characters in the familyName or styleName ufo2fdk will automatically create a f=1 and s=1 in FontMenuNameDB encoded for mac.
see http://code.typesupply.com/browser/packages/ufo2fdk/trunk/Lib/ufo2fdk/makeotfParts.py#L80
Its adding the metrics of the first component added.
In the next update there will be a checkbox where you can enable copying metrics from the base glyph.is it possible to send the UFO file to info at typemytype dot com
thanks
:P
if its enabled it will use the embedded FDK, if not RoboFonts tries to use the the local installed FDK, if you dont have a FDK installed you are not able to generate binaries.
If you want to check if FDK is installed type “which makeotf” in your Terminal. This should return some similar like “/Users/
/bin/FDK/Tools/osx/makeotf”
mmm no, RoboFont only talks to the FDK which is set as default. The FDK that responds to “makeotf” in Terminal.
Is there a reason why you want to use an older version of the FDK?
you have multiple FDK on your local machine?
RoboFont will use the FDK that is responding when you type “makeotf” in terminal