designSpaceDocument
designSpaceDocument copied to clipboard
LettError
Python reader and writer object for designspace files.
See https://github.com/googlei18n/glyphsLib/issues/336#issuecomment-377710826 and the following 2 comments. This should be in the documentation. Do you still accept PRs or should I send them elsewhere, now that designspaceDocument is moving to...
see https://github.com/LettError/designSpaceDocument/blob/master/Lib/designSpaceDocument/__init__.py#L1132
If the designspace document has a `map` element, it is desirable that one be able to define instance locations in either the "user" space or "design" space. The default IMO...
Erik, how about we move the `designSpaceDocument/__init__.py` module into a new `fontTools.designspace` module (or if you prefer camelCalse, `fontTools.designSpaceDocument`)? Only the generic part, not the ufo specific one (for now...
@LettError: Maybe this is a way to add AxisValueNames into DSD? Only added things to the 'write' part of code. ``` xml ```
When glyphsLib converts a multiple-master glyphs file into a set of UFOs + a designspace file, we lack the ability to store Glyphs.app specific data such as instance custom parameters...
The OpenType `name` table supports localized family and style names. Likewise do font editors such as Glyphs. If the designspace document format supported this, glyphsLib could copy the localized names...
@behdad @LettError I often find myself building interpolatable TTFs using "other" tools (e.g. FontLab). Or I use the UFOs but then once the interpolatable TTFs are built, I postprocess them....
