-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use otData for dict to COLR conversion #2181
Conversation
83ffec6
to
74638ab
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there's a few issues, I left comments inline. I have to say this does increment the level of complexity (potential hidden bugs, difficulty of maintaining, etc.) a little bit. Hopefully that's a good trade-off and I will just get used to that.
e5ff272
to
5fa9d0f
Compare
5fa9d0f
to
ea3a939
Compare
I've somehow lost your comment about why meddle with the optional version. Note that I put that back to how it was before. |
d3cc857
to
385bb5a
Compare
c929f4b
to
6538947
Compare
6538947
to
cf4a408
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Made a last few tweaks, ptal, hopefully safe to merge now. |
0fa0d9b
to
274a753
Compare
Co-authored-by: Cosimo Lupo <cosimo@anthrotype.com>
274a753
to
0353c80
Compare
Writing per-format functions is tiresome, try to avoid it by leaning on otData. Setting up as PR because I think it's far enough along it might be convenient to be able to comment.