it will remove the glyph name from all groups in font.groups
and it will remove the kerning pair of one of two is equal to the removed glyph
so when a user removes glyph 'A', it will remove (if those settings are enabled):
Thanks a lot, it does the trick.
Note to users: ## print them nicely means with a wordspace between each glyph. For proofing, I need to get rid of the space, so I simply removed it between the quotes:
print " ".join(allGlyphs) → print "".join(allGlyphs)
from Matthieu's email:
What I mean by slow down is that every time I place a point, there's a lag between placing it and pulling the handle. This should be immediate, which is the case when there isn't any bitmap image.
There is a tiny distance that the mouse has to move before a bcp is added. RoboFont is doing so to prevent unnecessary adding bcp. But it seems like the zoom level isnt really taking into account to calculate the minimal mouse dragged distance in order to create/add a new bcp
hope this make sense and will be solved in the next version.
I think you disabled "Use Embedded FDK" and on your local machine there is no FDK installed, so RoboFont cannot find anything to generate the binary file.
RoboFont will check the splines and convert them to two off curves splines in the next version.
(in version 1.1 it doesn't check WOFF files, but it should
Although WOFF files with PS outlines should work fine.
Bonus answer: no
Yes there will only work in RoboFont, but some have some similarities with the special FL robofab methods.
It doesnt matter if you imported it from mojo.roboFont or robofab.world (inside RoboFont) all robofab object will have these additions.
Why is info a dict instead of an instance of a reall class defined in mojo.events?
I ask about source code because __doc__ seems to be empty for all the mojo.* modules and classes, and the API documentation is missing a lot. I'm looking for a way to supplement my understanding of the API without asking you a hundred questions.
If you have a python package installed in the current python on your local machine, that package will be accessible in RoboFont.
RoboFont is adding the site-packages of the current python to the sys.path.
So if you have a python package that can read from a serial port it must be possible to access that package in RoboFont
Plausible point of view.
(The spec isn't the problem, but it's sometimes problematic to operate in a world where many people are not following the spec (and end-users suffer). In a world where font foundries and application developers are making workarounds for each others workarounds, it's meanwhile impossible to define who is the chicken and who's the egg. Indeed, we're way off topic…
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/<userName>/bin/FDK/Tools/osx/makeotf"