"That"? can be an adjective, conjunctive or some other stuff, you can look it up?
In other news, Plex, e.g. has 2 binaries published. Decovar has two ufos published. Not an easy spot to openly develop, to or from. And there is not just one reason for these things. But it is one reason I always start with a 2048 quadratic master. And the facts that 1. no font tool will open other tool's binaries and generate the same binary, and 2. no two font tools will open the same binary and generate the same binary and 3. no source format can be opened by all tools, and even if it could be 4. no two tools would generate the same binary from that same source, 5. and no tools actually help the user much to know the effects of mods they make, ...all mean mods can happen all over the place that are not known to the casual or intermediate modifier. So, right now, I think, you rationalize "open source" to mean whatever it can. Later, is the future. That's all that means.
That’s all great but the infrastructure of line layout and variables were intended to be implemented together, not Separated by 25 years and artificial barriers of the technologies that grew in between. So it’s always interesting to see what’s going wrong just because of the past politics, and how little has changed in “round two.”
John’s points touch on an interesting set of issues related to but not of VUID and VOTF. Variable components are one issue. We’ve provided an example of that in Decovar. There are two sets of masters because of the disconnect we think there is between nested variable components and variable glyphs. I’m not sure John’s proposal to change the font format will solve that, but because it is common enough, and John isn’t, I just assume so. By common enough, I think a lot of people recognize the need to build glyphs from variable components, and by uncommon enough, Johns experience in this is great.
It’s importent to write though, that our Google Font projects were not focused back on these issues yet. Nor was our proposal scoped to allow any request for change to the font format. Just the fundamental axes we thought obviously need to be added. These were specified, in some cases, to make the need for format change, or at least further discussion, more obvious. The Overhanging obviousness we are heading to, is that there needs to be little, or better, no difference, between the font format and the design format. As that is something that could take years, we do what we can, now.
So, we agree that the assembly of glyphs from variation space is one issue. Having discovered for ourselves in Decovar, the variable component side of things, and more, we also stand by all of the proposal and I expect that later change to the format will make some of it much more clear. Ahead of that clarity, we think, demonstrate and progress on our need to go into variation space for parts, and for whole glyphs. So, I’m not sure why one thing there would be Important Enough to change the font format while the other thing there is Not Important Enough to register as an axis.