That particular addition to the language is not in common usage. To have someone not know its meaning isn’t any real indication of anything, except for a persons level of familiarity with lightwave..
Ahh, now I understand. I think…
In any case, I really think it’s a lot more than Lightwave. I believe Modo uses them. And I’m sure that other apps also use them. And even if you don’t work in those apps, anyone who has to import/export from any of those apps needs to understand of their existence to know how to deal with them. Which is why I raised the issue.
And IF (though I’m not sure this is the case) the code in many/most modellers ALLOWS the unintentional creation of 1-point or 2-point polygons, then you need to be able to deal with them.
Back to the OP’s original problem, IF they were generated in Hex somehow (and, not knowing the inner workings of all the modelling apps, that seems it might be at least possible), then it becomes a very important consideration in fixing the problem.
So whether the average guy on the street refers to 1-point or 2-point polygons, or whether Andy and Garstor believe they make sense, is kind of irrelevant if you have a model that has them and you have to fix it.