Tags from MutatorMath

3.0.1

2020-04-24T09:20:12Z

3.0.1

Update version in setup.py to match git tag.

3.0

2019-09-04T12:56:30Z

2.1.2

2018-11-01T19:36:04Z

Release 2.1.2

- Removed ufoLib dependency. Bumped minimum fonttools >= 3.32.0.
- Added ``bend=True`` flag for makeInstance; allows instances to be
calculated without the bender transformation.
This is sometimes necessary.

2.1.1

2018-06-07T10:01:21Z

Release 2.1.1

- Assume incoming locations might be plain dicts and wrap them (#110).
- Don't fail when reading designspace documents with `format` attribute
formatted as a float, as in latest designspace spec (#117).

2.1.0

2017-11-06T12:48:17Z

Release 2.1.0

- [ufo.document] Added API to generate a single instance, useful when
parallelizing build for fonts with large number of instances.
The DesignSpaceDocumentReader has a new `readInstance` method that reads
and builds a single instance element. It takes a `key` tuple argument
with the (attribute, value) used to find and select the instance to build.

2.0.7

2017-10-25T14:50:28Z

Release 2.0.7

- Write forward slashes as path separators (#95).
- Replace Adobe Sans test font with new data with similar range in width
and weight, covered by the same license as this package (#96).

2.0.6

2017-10-02T16:12:45Z

Release 2.0.6

Updated minimum requirements:
* defcon >= 0.3.5
* fontMath >= 0.4.4

2.0.5

2017-10-02T15:52:14Z

Release 2.0.5

Allow multiple unicode values for glyphs (#86).

2.0.4

2017-04-12T22:17:44Z

2.0.4

- Fixed problem caused by files in which a source element has no "name"
attribute, by adding a temporary simple unique name (#80).
- The designspace document description now lives at the designSpaceDocument
repository: https://github.com/LettError/designSpaceDocument.
- Pass UFO groups to the MathKerning object so that the latter is able to
identify the exceptions (#82).

2.0.3

2017-03-15T15:47:46Z

2.0.3

[bender] Properly handle split locations (i.e. anisotropic interpolation) in
the WarpMutator and Bender classes (1ed6581).

Note: If you happen to write your own warp functions (so, not the maps, but
actual python function objects), these functions need to handle tuple values
as well.