skef

(Which, it's worth noting, actually works just fine now *except* for this problem of initial axis values. All the other stuff remains entirely workable with only "extreme" masters.)

And you're saying that the font engineer will still have reasonable intuition for how the user space maps to the internal space space when debugging issues, etc?

In terms of axis positions, Adobe is generally pursuing a design in which the designer can use the units they think appropriate to the situation, picked with a suffix, and...

Incidentally, on the recurring "assembly language" metaphor: Even if almost all development switched entirely to higher-level tools, and it is far from obvious this will happen anytime soon, our situation...

@behdad Whether axis specifications are needed from the start of a feature file depends on whether, in a VF-first workflow, we're thinking that the designspace file is going away, which...

@rsheeter As far as your narrow question, my current notes have "u" for user units, which as I said would be the default if omitted. Design units would be "d"...

In that case, the only additional unit set that I've considered is one that goes from 0 to 1 or perhaps 0 to 1000, which would be analogous to "n"...

I only have user coordinates as the default in my notes because I was under the impression that current ad hoc VF-first support in feature files (in, e.g. fonttools) used...

`tx` translates the various PostScript-like CharString formats into callbacks of this form: ``` struct abfGlyphCallbacks_ { void *direct_ctx; void *indirect_ctx; abfGlyphInfo *info; int (*beg)(abfGlyphCallbacks *cb, abfGlyphInfo *info); void (*width)(abfGlyphCallbacks *cb,...

Thinking about this, I suppose what just testing for intersections would miss is a contour with the same direction entirely within another contour. There might be corner cases in VF...