-
Notifications
You must be signed in to change notification settings - Fork 51
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
hints: target="up" or "down" #613
Conversation
@madig do we need to check target="down" or target="up" only occurs with type="TopGhost" or "BottomGhost" respectively? |
7e8a337
to
c91b124
Compare
No idea. @schriftgestalt ? |
This is true. Is this answering the question? |
c91b124
to
af15d6a
Compare
Yes, thanks! I guess glyphsLib doesn’t need to validate. |
b611620
to
cc5d43a
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.
What's the status of this?
BTW, I think the flake8 errors should pass after rebasing or merging master onto this.
if attr in hint: | ||
value = Point(*hint[attr]) | ||
# handle target = ['u', 'p'] or ['d', 'o', 'w', 'n'] |
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.
@moyogo why do we need to handle target = ['u', 'p'] or ['d', 'o', 'w', 'n']
? Is that for backward compat with how these attribute was written out to UFO before this PR? If so, maybe add a comment with a link to the issue
cc5d43a
to
568ee04
Compare
Added a glyph to GlyphsUnitTestSans thus changing indeces of glyphs that follow.
568ee04
to
a82c2ad
Compare
See Hints: handle up and down targets #376