1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
|
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<!-- The top level `axes` key defines a list of axis definitions -->
<key>axes</key>
<array>
<!--
Each axis definition must have a `name` and the axis `tag` (duplicate
the information from the Designspace). `locations` is optional, if you
only use format 4 axis values, you don't need to define `locations` on
an axis.
Note that `name` can always be either a string or a dictionary of IETF
BCP 47 language codes to name strings. See "Regular" below for how this
looks like. If it is a string, it will be used to create a name table
entry with it for the language "en" or language ID 0x0409. If it is a
dictionary, it will automatically create appropriate multilingual name
table entries.
The `name` of an axis is a special case: You can define a dictionary
with name mappings, but it's only going to be used if the axis doesn't
already exist in the fvar table. Reason: you can use the `labelname`
element in the `axis` element in a Designspace to define multilingual
names. You can't when you don't define the axis, so you can do it in
the Stylespace instead.
-->
<dict>
<key>name</key>
<string>Weight</string>
<key>tag</key>
<string>wght</string>
<!--
`locations` are a list of dictionaries describing stops on the axis. Each
dictionary models one of format 1, 2 and 3 of the STAT axis values.
-->
<key>locations</key>
<array>
<!--
Format 1 must have at least `name` and `value`. `flags` is optional, see
below.
IMPORTANT: The `value` always means value in user space like in the
fvar table!
-->
<dict>
<key>name</key>
<string>XLight</string>
<key>value</key>
<integer>200</integer>
</dict>
<dict>
<key>name</key>
<string>Light</string>
<key>value</key>
<integer>300</integer>
</dict>
<!--
Format 3 must have at least `name`, `value` and `linked_value`. `flags` is
optional.
-->
<dict>
<!-- This is an example of how to define multilingual names. -->
<key>name</key>
<string>Regular</string>
<key>value</key>
<integer>400</integer>
<key>linked_value</key>
<integer>700</integer>
<!--
Flags is a list and can contain the strings "ElidableAxisValueName",
"OlderSiblingFontAttribute" or both.
-->
<key>flags</key>
<array>
<string>ElidableAxisValueName</string>
</array>
</dict>
<dict>
<key>name</key>
<string>Semi Bold</string>
<key>value</key>
<integer>600</integer>
</dict>
<dict>
<key>name</key>
<dict>
<key>en</key>
<string>Bold</string>
</dict>
<key>value</key>
<integer>700</integer>
</dict>
<!--
Format 2 must have at least `name`, `value` and `range` with (min,
max) values. `flags` is optional.
-->
<dict>
<key>name</key>
<string>Black</string>
<key>value</key>
<integer>900</integer>
<key>range</key>
<array>
<integer>701</integer>
<integer>900</integer>
</array>
</dict>
</array>
</dict>
<dict>
<key>name</key>
<string>Italic</string>
<key>tag</key>
<string>slnt</string>
<key>locations</key>
<array>
<dict>
<key>name</key>
<string>Upright</string>
<key>value</key>
<integer>0</integer>
<key>linked_value</key>
<integer>1</integer>
<key>flags</key>
<array>
<string>ElidableAxisValueName</string>
</array>
</dict>
<dict>
<key>name</key>
<string>Italic</string>
<key>value</key>
<integer>1</integer>
</dict>
</array>
</dict>
</array>
<!--
The top-level `locations` key is a list of format 4 axis values. It is
optional and can be left out from the Stylespace if you don't need format
4 axis values.
ATTENTION: Using format 4 axis values bumps the STAT table version from 1.1 to
1.2. At the time of this writing (February 2019), version 1.2 is not supported by
Windows.
-->
<key>locations</key>
<array>
<!--
A format 4 dictionary must contain `name` and `axis_values`, the latter
is a dictionary of axis names to values. `flags` are optional.
-->
<dict>
<key>name</key>
<string>ASDF</string>
<key>axis_values</key>
<dict>
<key>Weight</key>
<integer>333</integer>
<key>Italic</key>
<integer>1</integer>
</dict>
</dict>
<dict>
<key>name</key>
<string>fgfg</string>
<key>axis_values</key>
<dict>
<key>Weight</key>
<integer>650</integer>
<key>Italic</key>
<real>0.5</real>
</dict>
<key>flags</key>
<array>
<string>ElidableAxisValueName</string>
</array>
</dict>
</array>
</dict>
</plist>
|
