Hi, is this a suitable place for raising OpenType spec issues?
For example, in the GSUB header struct the spec implies that scriptListOffset, featureListOffset, and lookupListOffset cannot be NULL, as offsets that can be NULL have a comment saying "may be NULL" (such as the featureVariationsOffset field).
However, existing fonts such as Noto Glagolitic do have NULL values for these offset fields and I haven't found any implementation that actually requires them not to be NULL or emits any errors or warnings during font validation if NULL offsets are encountered.
Since it would be helpful for the spec to describe how to create an interoperable implementation, perhaps these fields could be changed to "may be NULL"? A similar issue affects the GPOS header struct.
Hi, is this a suitable place for raising OpenType spec issues?
For example, in the GSUB header struct the spec implies that scriptListOffset, featureListOffset, and lookupListOffset cannot be NULL, as offsets that can be NULL have a comment saying "may be NULL" (such as the featureVariationsOffset field).
However, existing fonts such as Noto Glagolitic do have NULL values for these offset fields and I haven't found any implementation that actually requires them not to be NULL or emits any errors or warnings during font validation if NULL offsets are encountered.
Since it would be helpful for the spec to describe how to create an interoperable implementation, perhaps these fields could be changed to "may be NULL"? A similar issue affects the GPOS header struct.