Ned Holbrook

Straw proposal: `dmap` mapping to 0 (whether due to explicit mapping or no entry) means “use cmap”, and `dmap` mapping to a value greater than or equal to the number...

I would say this is still fairly important, especially for characters like punctuation that may occur in either visual order. Not sure this requires more bits, though: my strawman suggestion...

My thinking here was to broaden the use of the flag beyond CursivePos but you raise a good point in allowing direction flags to affect it too. > I think...

My concern is that without a version break old clients might get dramatically different layout, making it difficult to deploy fonts using the new flags.

So where does that leave us? Should the new flags only be valid for new lookup types?

If my understanding is correct, the request here is to allow avar2 (or something else, perhaps an `fvar` flag) to enable variation processing for what would otherwise be the default...

Running the tool just now gives me the same exception but for a different property: ``` Modifier_Combining_Mark 15.1.0.0 com.ibm.icu.util.ICUException: Modifier_Combining_Mark( from: /Volumes/Common/projects/unicode/unicodetools/unicodetools/data/ucd/15.1.0/PropList.txt) at org.unicode.props.IndexUnicodeProperties.load(IndexUnicodeProperties.java:492) at org.unicode.props.IndexUnicodeProperties.load(IndexUnicodeProperties.java:454) at org.unicode.propstest.CheckProperties.compare(CheckProperties.java:656) at org.unicode.propstest.CheckProperties.main(CheckProperties.java:219)...

> Scripts.txt has no missing ranges You’re right, I was thinking about ScriptExtensions.txt but my brain expanded the set.