search

MPEGGroup / OpenFontFormat

Official MPEG repository to discuss issues on Open Font Format (ISO/IEC 14496-22)
31 stars 6 forks source link

Register one catch-all required feature? Add direction hints to lookups? #16

Open davelab6 opened 3 years ago

davelab6 commented 3 years ago

In https://lists.aau.at/pipermail/mpeg-otspec/2018-April/000030.html @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?
behdad commented 3 years ago

On Sun, Sep 20, 2020 at 9:08 PM Dave Crossland notifications@github.com 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.