Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[otvar] Rule conditionsets conflict with OT layout (shaping)

See original GitHub issue

Considering this .designspace excerpt:

    <rule name="ra_crossing">
      <conditionset>
        <condition name="weight" minimum="625" maximum="700"/>
      </conditionset>
      <sub name="uni170D" with="uni170D.avar"/>
    </rule>

And this OTLayout feature:

# Ra to archaic Ra
feature hist {
  lookup hist_1 {
    sub uni170D by uni171F;
  } hist_1;
} hist;

Why, when hist is active, does a wght ≥ 625 cause uni170D, shaped to uni171F, to become uni170D.avar?

To confirm that this bug exists, open https://ctrlcctrlv.github.io/baybayin/ , type <kbd>ra</kbd> as input, tick “Archaic ra” checkbox, and increase weight above 625.

Issue Analytics

State:
Created 3 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

ctrlcctrlvcommented, Aug 12, 2020

@justvanrossum Thanks for replying. Not at present, but I reserve the right to think of one!

🤔 💭

0reactions

justvanrossumcommented, Aug 12, 2020

What .designspace supports is a high level simplification of what is theoretically possible with FeatureVariations, based on use cases we were aware of at the time. While what you suggest is possible, it would make everything a lot more complex.

Do you have a specific use case in mind where this could be handy?