You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently, when compiling value records, we skip null values. This means it is currently impossible for us to correctly compile a value record which contains a null device offset, even if this is expected, and the ValueFormat indicates such a table will be present.
If this occurs, we will silently produce an incorrect font.
This is not a very likely scenario, but it is still something we need to address.
The solution to this will likely be some slightly fancier way of indicating custom compilation behaviour.
The text was updated successfully, but these errors were encountered:
currently, when compiling value records, we skip null values. This means it is currently impossible for us to correctly compile a value record which contains a null device offset, even if this is expected, and the ValueFormat indicates such a table will be present.
If this occurs, we will silently produce an incorrect font.
This is not a very likely scenario, but it is still something we need to address.
The solution to this will likely be some slightly fancier way of indicating custom compilation behaviour.
The text was updated successfully, but these errors were encountered: