[OpenType] RE: Proposal: deprecate ReqFeatureIndex

John Hudson john at tiro.ca
Wed Aug 22 23:14:39 CEST 2012

On 22/08/12 1:39 PM, Peter Constable wrote:

> E.g., I might want to specify (say) ss01 and ss02 as required for a particular language but still keep them separate because each triggers groups of lookups that are useful as distinct groups for some other scenario. It's true that I could keep ss01 and ss02 as is but create ss03 that combines the lookups associated with ss01and ss02 and use that as the required feature for some given language system, but there might be reasons why I wouldn't want to do that--e.g. if I needed to support many languages with different behaviours, I might find it a better way to do things.

But using Behdad's suggested approach, to which I am coming around, you 
would be able to create an arbitrary feature tag, e.g. <reqd>, and 
easily associate the Stylistic Set 1 and 2 *lookups* with that feature, 
and then the feature with the ReqFeatureIndex.

The kind of situation you describe is only a problem if one assumes that 
ReqFeatureIndex has to point to a single registered feature, rather than 
to a feature that is simply a collection of required lookups for a given 
language system.



Tiro Typeworks        www.tiro.com
Gulf Islands, BC      tiro at tiro.com

The criminologist's definition of 'public order
crimes' comes perilously close to the historian's
description of 'working-class leisure-time activity.'
  - Sidney Harring, _Policing a Class Society_

More information about the mpeg-otspec mailing list