Rod

I agree it would make it somewhat harder to handwrite. Todays main source formats tightly couple user and design units. Do we know how that will change for avar2? Is...

https://github.com/adobe-type-tools/afdko/pull/1350#discussion_r636008312 specifically says user coords. Presumably it did not consider avar2 complications.

> > [adobe-type-tools/afdko#1350 (comment)](https://github.com/adobe-type-tools/afdko/pull/1350#discussion_r636008312) specifically says user coords. > > Yeah, but as per [#94 (comment)](https://github.com/harfbuzz/boring-expansion-spec/issues/94#issuecomment-1604770895) I think that's just wrong. Under avar2 I agree, just highlighting because OP says...

> That breaks the desirable condition that designer can tweak avar mappings at the end of design work freely, without needing to modify the masters. Ty, I was not aware...

@skef ty for the update, that's very helpful as we build out fea-rs. Would it be possible to share the unit suffixes you are thinking of, even if they are...

I would prefer the feature file just assume the compiler can translate units. Whether information came from a .designspace or .glyphs or is out of scope for fea, it just...

What do you mean by "layer font"? Can you point out examples?

Ty for the reminder. We did Bungee, https://fonts.google.com/?query=Bungee+Spice. @davelab6 are there other examples we should look at?

+1 to the horrors of transparent overlapping shapes! See https://github.com/googlefonts/colr-gradients-spec/issues/199 for some prior discussion. Worth contemplating as part of either a COLRv2 or the so-called "boring expansion" (https://github.com/be-fonts/boring-expansion-spec).

Vigorously agree with both "This is stepping into a very non-trivial requirements minefield." and "The current ambiguity is a big problem." I like the general idea of saying what currently...