PeterCon
commented
4 years ago Can you elaborate what you have in mind? The intent isn't clear in a few ways:
- Should all ten bytes vary independently? Only certain of the bytes?
- The meaning of some bytes is dependent on the value of other bytes. Should there be constraints, e.g., don't vary a byte if it causes the interpretation of another byte to change?
- All of the bytes assign meaning to integer values, so the continuous (floating point) nature of detail values isn't an obvious fit.
- Even allowing for the discrete nature of integer values, some of the bytes clearly aren't on a numeric scale—certainly not family type or tool kind.
These aren't insurmountable, and clearly some things in the PANOSE system use continuous numeric scales (that get discretized to byte values in specified ways). But some clarification is needed.
davelab6
MVAR table should support panose values.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.