On Thursday 29 January 2015 08:17 PM,
Dave Crossland wrote:
Agree with you. We will do comparison.
AFDKOs libre version doesn't include the
removeOverlap() method, so you need something else to do that,
and fontforge improved its version substantially last year.
Fontforge also improved its UFO support, such that
you can use it to develop UFO+FDK projects (like Adobe Source
However, Fontforge has supported importing and
exporting fea files for many years, and is scriptable for
command line use.
Before deciding to switch, I recommend setting up
both a fontforge and fdk based workflow from the same source and
comparing the resulting binaries, and also considering how
maintainable and comprehensive each is.
I am thinking for at least one change is to use makeotf for building
ttf. I think OTM and Fontlab using it in the backend. So good if we
can build Lohit ttf also with it.
On Jan 29, 2015 3:18 AM, "Pravin Satpute"
I was thinking for this from some time now.
1. Lots of well know fonts are using AFDKO. AFAIK Adobe
fonts are build using AFDKO.
2. Things we required in Lohit specifically, easy to read
feature files and final ttf with Adobe glyph naming
guideline looks easily manageable with AFDKO. (GlyphOrderAndAliasDB
3. AFDKO feature file compilation is much better than
Fontforge. Noticed this earlier with OTM errors. Also while
compiling i found number of error not identified by
4. All command line, so we can automate very nicely.
5. We will use fontforge only for outline related work.
Presently we are still using fontforge for OpenType rules
writing, i have not faced any problem into it yet. But
perfect solution is we should write open type rules in .fea
file itself. This at least not targeting presently
Lohit-devel-list mailing list
i18n mailing list