shadowfacts/fonttools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #3298 from fonttools/dslib-accept-always-on-rules

Browse Source 
designspaceLib: Accept empty condition sets
This commit is contained in:
Nikolaus Waxweiler 2023-10-26 10:05:30 +01:00 committed by GitHub
commit 541c6cd201
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Doc/source/designspaceLib/xml.rst
View File

@ -457,7 +457,7 @@ glyphname pairs: the glyphs that need to be substituted. For a rule to be trigge
- Defines a named rule.
- Each ``<rule>`` element contains one or more ``<conditionset>`` elements.
- **Only one** ``<conditionset>`` needs to be true to trigger the rule (logical OR).
- **Only one** ``<conditionset>`` needs to be true to trigger the rule (logical OR). An empty condition set is considered to be true, as in, the rule will be always-on.
- **All** conditions in a ``<conditionset>`` must be true to make the ``<conditionset>`` true. (logical AND)
- For backwards compatibility a ``<rule>`` can contain ``<condition>`` elements outside of a conditionset. These are then understood to be part of a single, implied, ``<conditionset>``. Note: these conditions should be written wrapped in a conditionset.
- A rule element needs to contain one or more ``<sub>`` elements in order to be compiled to a variable font.
@ -475,7 +475,7 @@ glyphname pairs: the glyphs that need to be substituted. For a rule to be trigge
--------------------------
- Child element of ``<rule>``
- Contains one or more ``<condition>`` elements.
- Contains zero or more ``<condition>`` elements.
``<condition>`` element