Lines Matching refs:That
12 A couple of differences between things that use designspaces:
25 objects that store the data in attributes. Data is added to the document
53 location uses an axis that is not defined it will be ignored.
55 axis names, so that we can..
78 dictionaries using the language code as key. That means that there are
88 glyphname pairs: the glyphs that need to be substituted. For a rule to be triggered
92 The ``sub`` element contains a pair of glyphnames. The ``name`` attribute is the glyph that should be visible when the rule evaluates to **False**. The ``with`` attribute is the glyph that should be visible when the rule evaluates to **True**.
98 that the original shape is still available. For instance, if a rule
99 swaps ``a`` for ``a.alt``, but a glyph that references ``a`` in a
101 - But that can lead to unexpected results. So, if there are no rules
102 for ``adieresis`` (assuming it references ``a``) then that glyph
103 **should not change appearance**. That means that when the rule swaps
104 ``a`` and ``a.alt`` it also swaps all components that reference these
127 this source font that is loaded in memory, as a Python object
133 disk and make ``filename`` point to that.
152 - ``mutedGlyphNames``: list. Glyphnames that need to be muted in the
287 - ``map``: list of input / output values that can describe a warp of user space
399 - ``name``: required, string. Name of the axis that is used in the
527 - Defines a single font that contributes to the designspace.
539 - ``name``: required, string. A unique name that can be used to
665 - Defines a single font that can be calculated with the designspace.
682 - ``name``: required, string. A unique name that can be used to
868 - ``name``: optional, string. A unique name that can be used to
968 **near** each other, and that they can be **found** without enforcing
1056 difference is that applications using a Designspace as the corner stone of the
1057 font compilation process should use the lib key in that Designspace instead of
