Another contextual anchors question: Is it possible to specify the order of application, such that more specific contexts run before less specific ones? i.e. if I have an anchor with context
fehDotless-ar.init.ain @ArabicDots * @KAFm
I would like that to appear in the feature code before another anchor with a more general context:
fehDotless-ar.init.ain @ArabicDots *
I was thinking about that. I decided against it as it would probably need a better UI (not only that single text field) to be useable.
What would be the full string?
Not generally. But if it would be on the same anchor (and we decide to implement this), then the order should be preserved.
That was a separate question: two different anchors, one with a specific context and one with a more general one. The specific one should go first.
how to determine specificness?
Also the use of & to place mark name is not documented.
Both are very recent additions. There is still room for these to change until the 3.2 release which is when the Handbook will be updated to document the latest stable features.