robotools / ufo2fdk Goto Github PK

I think it might have to become glyph.controlPointBounds[0]

it is possible that the maxY is negative in exceptional cases

see fonttools/fonttools#520

@typefactory

See unified-font-object/ufo-spec#84. This is in ufo2ft.

FDK is changing tools and it possible that checkoutlines is not available anymore in favour of checkOutlinesUFO when installing FDK from source.

@adobe-type-tools could you confirm this?

This might be an edge case but I am attempting to build a family with a very large amount of fonts. My build script uses the execute function in the FDKBridge.py but breaks around 125 fonts with the following error: OSError: [Errno 24] Too many open files. It seems to be a problem with the line where popen is declared.

https://github.com/adrientetar/ufo2fdk/commit/79d3430420bcb053c73db7ee14a60e2e7452f2d4

Store the GOADB here:

com.typesupply.ufo2fdk.glyphOrderAndAliasDB

Some new UFO3 font info attributes don’t have a fallback in ufo2fdk.fontInfoData.

Running the script below in RoboFont 2 will print the missing attributes:

from ufo2fdk.fontInfoData import *

f = NewFont()
f.info.familyName = 'Hello'
f.info.styleName  = 'World'

for attr in sorted(f.info.asDict()):
    try:
        getAttrWithFallback(f.info, attr)
    except:
        print attr

openTypeGaspRangeRecords
openTypeNameRecords
openTypeOS2WinAscent
openTypeOS2WinDescent
woffMajorVersion
woffMetadataCopyright
woffMetadataCredits
woffMetadataDescription
woffMetadataExtensions
woffMetadataLicense
woffMetadataLicensee
woffMetadataTrademark
woffMetadataUniqueID
woffMetadataVendor
woffMinorVersion

K:\del\robofab-master\robofab-master>python setup.py install
File "setup.py", line 15
print "*** Warning: FontTools needs the numpy library for some operations, see:"
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("*** Warning: FontTools needs the numpy library for some operations, see:")?

see adobe-type-tools/afdko#682

this should change here https://github.com/typesupply/ufo2fdk/blob/master/Lib/ufo2fdk/makeotfParts.py

Currently the default values for defaultWidthX and nominalWidthX are 200 and 0 and they are never adjusted according to the glyphs in the font. This makes for a slightly bigger CFF table when compared with what makeotf produces.

otf-making-benchmark has two test cases.

This should maybe be handled nicely by ufo2fdk

see adobe-type-tools/afdko#47

this brings up an other issue: It would be nice to send ufo2fdk a list of pre process and post process callbacks, this could be a solution to add both callbacks defined in ufo2fdk as custom callbacks. Similar to extractor customFunctions.

See here: #3

See this PR for details:

#7

Address this by joining the strings with u"\n\n" instead of "\n\n".

cc @adrientetar