The examples in GSUB and GPOS are very helpful, but it would improve readability a lot if there was an additional "Hex Offset" column (at least in the expanded version of the tables) that shows at which Hex address the data for each row is stored.
With this extra column, offsets are much easier to see, which currently is very hard IMO.
Here is a quick and dirty spreadsheet mockup of Example 8 in GPOS (which I am currently trying to implement). The arrows only indicate why the colum would be helpful:
This is not absolutely crucial, but as written above, it would improve readability of the examples quite a bit.
Description
The examples in GSUB and GPOS are very helpful, but it would improve readability a lot if there was an additional "Hex Offset" column (at least in the expanded version of the tables) that shows at which Hex address the data for each row is stored.
With this extra column, offsets are much easier to see, which currently is very hard IMO.
Here is a quick and dirty spreadsheet mockup of Example 8 in GPOS (which I am currently trying to implement). The arrows only indicate why the colum would be helpful:
This is not absolutely crucial, but as written above, it would improve readability of the examples quite a bit.
Page URL
https://learn.microsoft.com/en-us/typography/opentype/spec/gpos
Content source URL
https://github.com/MicrosoftDocs/typography/blob/live/typographydocs/opentype/spec/gpos.md