chrissimpkins
commented
7 years ago cc: @spstarr @paride
Sean and Paride,
@iamjamestl is developing an autotools based, highly configurable (at build time) typeface build approach here based upon the build tooling that we are using in Hack. The goal is to support build time customization of a number of aspects of font design (including hinting approach, font subset used, alternate glyphs used). This has the opportunity to provide users with the capacity to modify the fonts that they build at a very granular level in order to target specific needs (including platform specific rendering issues), aesthetic wants. It will also permit OS type developers to offer this type of build time configuration in a way that they currently cannot. It may also simplify the job of redistributors on Linux distros and we would be interested in your perspective re: this issue as this could/should be a goal here as well IMO. If there are benefits for all involved in the redistribution process the tooling might well be broadly adopted and will support increased access to distros that follow free software redistribution guidelines by typeface developers who want this.
Based upon James' response to the above suggestion, I am wondering if you would be willing to consider this autofont project for approval on Fedora and Debian (respectively) once we progress to a stable stage of development so that other users out there can build on your distros with "pre-approved" typeface build and post compile modification tooling according to your free software guidelines. As of now we do not have plans to deviate from the tooling that is already under review by both distros though it is possible that we may need to include additional dependencies as the work progresses and we identify new needs.
Since we are already going through the process for the Hack project, we may as well try to standardize this in a way that others can benefit from it.
Thoughts?
I suggest that we design the tool with the intent to support free, open typeface projects. Every aspect of the configuration piece (including hinting modifications, subsetting, glyph alternate swaps) will violate most, if not all, common commercial font licenses as non-free/open (including commercial) projects are generally not looking to allow user support for modification of their releases. Most of these licenses would need to be modified to support such a build time configuration tool.
If you agree with the above, then I suggest that we focus on tools within the build toolchain that are all free, open source software and that support common free software guidelines such as the Debian Free Software Guidelines. If we stick with such a design goal, any user of the tooling created here will be permitted to release their typefaces with these tools on platforms that abide by these software redistribution guidelines. This tool will be able to expand on the work that we have performed in Hack to push for access to additional FLOSS typeface compilation and post-compile modification software on distros including Debian/Ubuntu and Fedora in order to support use of autofont by any future typeface project without the need to go through the time intensive review process of build tooling by these distros. This will be a significant benefit for those who want to release their typefaces on Linux distros that build fonts from source files.