Both can keep all elements used in the font design process. Glyph names, OT features, text, layers, color, files, UI, Python, variaĭetecting Element References or CompositesįontLab offers two native file formats for saving: VFC (binary) and VFJ (JSON based). Variation, imported artwork, components, auto layers, elements Metrics, kerning, Font window, Font Info, hints, guides, classes What data/features are well preserved and which ones suffer some damages or are completely lost.General, editing, anchors, actions, FontAudit, copy-paste Perhaps a comparison of the various possible ways to transfer font projects. I suspect there may be a fair amount of potential to attract new users but they would need some information of this nature. I would think that now that FL6 has been released for almost half a year, it would make sense to provide some official help with this for anyone who may have grown frustrated by the state of FL6 (which still quite buggy and has a plethora of serious, fundamental problems with its core features which are ignored or unaddressed, updates and fixes are on a slow schedule and number of frustrated users’ questions go unanswered on the forum, if solutions don’t work there is often no further assistance). I haven’t been able to find much (anything really specific) about the best way to transfer a partially completed font project from FontLab VI to Glyphs. Although, that is in regards to FontLab Studio 5, not FontLab VI. ufo files exported by FontLab because data will lost, and that the macro is the better option. In one of the tutorials (I believe) it is advised that FontLab users avoid using. If any help, i can copy the whole macro output message in to thread.ĭid the script/macro work in FL6? If so, how would you rate the generated glyphs file? I’m pretty new to working with scripts so, i might have overlooked something obvious to the more trained eye. Will write font to: /Users/Jeppe/Documents/typoprojekter/Fl->ufoTest.glyphs

Synta圎rror: ‘utf8’ codec can’t decode byte 0x9f in position 4378: invalid start byte SystemError: dynamic module not initialized properlyįile “/Applications/code/RoboFab_599_plusAllDependencies/RoboFab/Lib/robofab/world.py”, line 94, inįrom import SelectFont, SelectGlyphįile “/Applications/code/RoboFab_599_plusAllDependencies/RoboFab/Lib/robofab/interface/all/dialogs.py”, line 169, inįrom _fontlab_legacy2 import *įile “/Applications/code/RoboFab_599_plusAllDependencies/RoboFab/Lib/robofab/interface/all/dialogs_fontlab_legacy2.py”, line 21, inįile “/System/Library/Frameworks/amework/Versions/Current/Extras/lib/python/PyObjC/Foundation/ init.py”, line 8, inįile “/System/Library/Frameworks/amework/Versions/Current/Extras/lib/python/PyObjC/objc/ init.py”, line 24, inįile “/System/Library/Frameworks/amework/Versions/Current/Extras/lib/python/PyObjC/objc/ init.py”, line 21, in _update The Macro Panel returns a loooong output message that starts as follows. The script creates a file, but it is Zero bytes, and Glyphs states it can’t be opened. I’ve downloaded the export script from Github( ) and stored it in the fontlab macro folder and then tried running it in the FL Macro Panel.

I know this subject has been touched upon before, but can’t seem to find a solution in previous threads.

Fontlab studio5