The W3C Internationalization Working Group has just discussed it:
We discussed this in today’s i18n WG meeting, and the consensus was that it’s not likely to cause ambiguity in the context of this document, so we decided to close the issue. Thank you.
—xfq, 2025-08-14
I have a feeling that they are all or mostly Chinese, which can explain why they don’t see the ambiguity, while two non-Chinese persons here do find it that way. And “in the context of this document” means that you have to read enough of it or wholly for ambiguity to go away. That’s not how it supposed to work, IMO.
The team discussed concerns about the term “gap” in typography-related documents potentially being misunderstood. Addison and xfq agreed that the context was likely clear.
—the meeting summary
I’m pretty sure they are all biased into knowing more stuff than regular people (in different senses and fields), hence less likely to agree on the matter.
Just as I’m biased into thinking that Typst language and scripting are very easy, yet a lot of general people with little to no knowledge/context will disagree. Well, if it’s their first non-natural language, then they are biased to say it’s hard, probably even if it were to be Python.
Yeah, knowledge bias definitely exists.
To be honest, I have no idea how big this ambiguity is (for English speakers), but if you want to change it, stronger evidence is required.
(For example, analyzing the proportions in a corpus?)