In the Glyphs XML, it is classified correctly as Mark, subcategory is Enclosing. In my client’s font, uni20DD has a center anchor. It is at 0 width, although it doesn’t have to be because Glyphs should zero it out. —and yet uni20DD still doesn’t get added to the GDEF.
This omission is reported as a WARN Font Bakery, which consequently gets confused and reports a FAIL because it thinks that uni20DD is a base glyph that should have space.
BTW, I tested renaming the glyph in the font to the name in the Glyphs’ XML, /enclosingcirclecomb, but that didn’t fix the error.
Enclosing marks take their space from the glyph that precedes it.
In my client’s case, we decided so unencode 20DD as it was just used as a part in drawing the encircled digits. Their dlig code does not use 20DD but rather the parens + digit. But, I wanted to report this bug anyway.
If the enclosing marks use the spacing from the base glyph, then they are just nonspacing marks. Unicode is much more specific about this than OpenType. In OpenType you can only distinguish between Base and (nonspacing) Marks.
So I need to change the SubCategory to Nonspacing. Thanks for the input.
