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
What I was hinting at was that maybe we should register one catch-all required feature that can be used in the future for any such things. Separating vertical might be the easiest currently. In some future we will add direction hints to lookups and then it wouldn't be needed anymore. Currently there's no such catch-all required feature. For GSUB, people do things with 'ccmp' or 'loca' which are supposed to be always on in all shapers.
Are these 2 suggestions still worth considering?
register one catch-all required feature?
add direction hints to lookups?
The text was updated successfully, but these errors were encountered:
davelab6
changed the title
Register one catch-all required feature?
Register one catch-all required feature? Add direction hints to lookups?
Sep 21, 2020
On Sun, Sep 20, 2020 at 9:08 PM Dave Crossland ***@***.***> wrote:
In https://lists.aau.at/pipermail/mpeg-otspec/2018-April/000030.html@behdad <https://github.com/behdad> wrote,
What I was hinting at was that maybe we should register one catch-all
required feature that can be used in the future for any such things.
Separating vertical might be the easiest currently. In some future we will
add direction hints to lookups and then it wouldn't be needed anymore.
Currently there's no such catch-all required feature. For GSUB, people do
things with 'ccmp' or 'loca' which are supposed to be always on in all
shapers.
Are these 2 suggestions still worth considering?
1. register one catch-all required feature?
2. add direction hints to lookups?
Yes. I'm happy to write proposals if there's a clear way how to make
technical decision and get it into the spec in a timely manner.
In https://lists.aau.at/pipermail/mpeg-otspec/2018-April/000030.html @behdad wrote,
Are these 2 suggestions still worth considering?
The text was updated successfully, but these errors were encountered: