Debian Codegraph @

googlefonts-qa/notes/outline-checks.md

raw
1 # Checking outlines after extrapolation
2
3 It was necessary to extrapolate a `Light` master to allow Fira Code to build via FontMake. As a result, some outline errors may have made their way into the glyphs in this new Master, because extrapolation is a useful but imperfect tool.
4
5 For the most part, I will abstain from fixing every little outline issue, because by and large, things here are well-drawn, and haven't been extrapolated in too extreme a manner.
6
7 ## General Process
8
9 I will use the Glyphs App extension Red Arrows to find potential problems, then check them over and fix what seems to be clearly wrong.
10
11 If it is not super obvious how to fix a potential issue, I will generally:
12 - Check what the Bold master does
13 - Check what Fira Mono (the ancestor of Fira Code) does in its Regular master
14 - Copy the existing layer to the background, and make that copied layer visible to provide a basic guide for my changes. For example:
15
16 ![](assets/2019-03-28-13-53-22.png)
17
18 I am not trying to change the design, but rather, to fix unintended vector issues that make the design less useful.
19
20 ### /U-cy
21
22 The main stem of this glyph has a "kink" that seems unintentional.
23
24 ![](assets/2019-03-27-13-35-37.png)
25
26
27 ### Zhedescender-cy
28
29 This has a component that isn't needed, and this juts out in the Bold master, causing an outline blip.
30
31 ![](assets/2019-03-27-13-41-12.png)
32
33 ![](assets/2019-03-27-13-40-23.png)
34
35 ![](assets/2019-03-27-13-39-56.png)
36
37 If we look at Fira Sans, it's clear what this shape is supposed to do:
38
39 ![](assets/2019-03-27-13-46-21.png)
40
41 The component was transformed to (10%, 10%) – way too small. I've adjust that to (85%, 100%) in the Bold and (100%,100%) in the light. Now it's like this:
42
43 ![](assets/2019-03-27-13-50-55.png)
44 ![](assets/2019-03-27-13-51-17.png)
45
46
47 ## Kastroke-cy
48
49 This crossbar is overly-thick, compared to others – I'll thin it out a bit:
50
51 ![](assets/2019-03-27-13-48-03.png)
52
53
54 ## Kahook-cy
55
56 Before:
57
58 ![](assets/2019-03-27-13-52-23.png)
59
60 Now:
61
62 ![](assets/2019-03-27-13-53-17.png)
63
64
65 ## Lha-cy
66
67 Mismatch in upper-left:
68 ![](assets/2019-03-28-13-40-08.png)
69
70 I removed the overlap in that stroke:
71
72 ![](assets/2019-03-28-13-42-04.png)
73
74 ## be-cy
75
76 The ascender has an issue:
77
78 ![](assets/2019-03-28-13-41-49.png)
79
80 ![](assets/2019-03-28-13-44-06.png)
81
82 ## ve-cy
83
84 Inflected curve:
85
86 ![](assets/2019-03-28-13-47-00.png)
87
88 ![](assets/2019-03-28-13-48-15.png)
89
90 ## ze-cy
91
92 (Almost certainly) unintended curve upwards:
93
94 ![](assets/2019-03-28-13-49-19.png)
95
96 ![](assets/2019-03-28-13-50-14.png)
97
98 ## ii-cy
99
100 Unintended upwards-handles.
101
102 ![](assets/2019-03-28-13-51-24.png)
103
104 The bold looks better:
105
106 ![](assets/2019-03-28-13-51-49.png)
107
108 So:
109
110 ![](assets/2019-03-28-13-56-45.png)
111
112 ### komije-cy
113
114 Ouch:
115
116 ![](assets/2019-03-28-14-03-53.png)
117
118 Better:
119
120 ![](assets/2019-03-28-14-04-50.png)
121
122
123 ### Chi
124
125 These feet aren't suppose to be angled so sharply:
126 ![](assets/2019-03-28-14-11-13.png)
127
128 In Fira Mono, you can see that the angle simply becomes less steep:
129
130 ![](assets/2019-03-28-14-13-00.png)
131
132
133 So:
134
135 ![](assets/2019-03-28-14-13-32.png)
136
137 ### kaiSymbol
138
139 Not-quite-vertical strokes:
140
141 ![](assets/2019-03-28-14-17-52.png)
142
143 Straightened in Bold & Reg:
144
145 ![](assets/2019-03-28-14-18-46.png)
146
147 ### betaSymbol
148
149 These lines are't supposed to intersect:
150
151 ![](assets/2019-03-28-14-20-11.png)
152
153 ![](assets/2019-03-28-14-21-39.png)
154
155 ### Nine
156
157 ![](assets/2019-03-28-14-24-45.png)
158
159 ![](assets/2019-03-28-14-25-49.png)
160
161 (similar problem in /nine.tosf)
162
163
164 ### asciitilde_greater.liga
165
166 Broken connection on right side:
167
168 ![](assets/2019-03-28-14-50-52.png)
169
170 ![](assets/2019-03-28-14-51-33.png)
171
172 ### asciitilde_asciitilde_greater.liga
173
174 Broken connection on right side:
175
176 ![](assets/2019-03-28-14-51-48.png)
177
178 I've just scooted the curvy thing towards the arrow by a bit.
179
180 ![](assets/2019-03-28-14-52-48.png)
181
182 ### uniE0A0
183
184 Broken connection:
185
186 ![](assets/2019-03-28-14-53-56.png)
187
188 Fixed:
189
190 ![](assets/2019-03-28-14-54-14.png)
191
192 ### r.001
193
194 ![](assets/2019-03-28-14-56-15.png)
195
196 ![](assets/2019-03-28-14-56-24.png)
197
198 ### ae
199
200 This curve isn't quite continuous:
201
202 ![](assets/2019-03-28-14-58-50.png)
203
204 I've made it a little more graceful:
205
206 ![](assets/2019-03-28-15-00-36.png)
207
208 ![](assets/2019-03-28-15-00-56.png)
209
210 ### "Incorrect smooth connections" in several glyphs:
211
212 Like these slight kinks:
213
214 ![](assets/2019-03-28-13-58-48.png)
215
216 Should be this:
217
218 ![](assets/2019-03-28-13-58-57.png)
219
220 ============================================================
221
222 ## (Small) issues I'm leaving
223
224 Often, crossbars have unnecessary points. These aren't really needed for the shapes and add a very small amount of data, but they're harmless, so I won't remove them right now.
225
226 ![](assets/2019-03-27-13-38-30.png)
227
228
229 ---
230
231 There are many instances of overlapping shapes that, while technically fine, might not render absolutely perfectly. I'll leave these, however, as they will probably bother no one.
232
233 ![](assets/2019-03-28-13-39-03.png)
234
235 ---
236
237 Small inflections, or semi-vertical handles that clearly should be that way:
238
239 ![](assets/2019-03-28-14-01-13.png)
240
241 ---
242
243 Some curvy shapes have slight issues around smooth connections. I'm looking at intermediate weights to make sure there aren't huge kinks (which is a concern in angled curve points), but otherwise mostly leaving these.
244
245 ![](assets/2019-03-28-14-10-07.png)