-
Notifications
You must be signed in to change notification settings - Fork 105
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
Check ligatures are consistent #2747
Comments
could you please clarify "exq thing"? |
Are we discussing here a proposal of a check specific to Or are we talking bout a broader issue that involves a larger set of potential ligatures? |
also...
|
Eqx, by sorkin type
…On Tue, Feb 11, 2020, 8:14 PM Felipe Corrêa da Silva Sanches < ***@***.***> wrote:
Assigned #2747 <#2747> to
@davelab6 <https://github.com/davelab6>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#2747>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB73S2ZUBWO3L5B6L3BM33RCNEQFANCNFSM4KOWUD5Q>
.
|
Yeah this could be an EQX pass fail question or possibly 2+ basic questions which build to a family consistency question. I'll have a look at this post Merriweather and revise the source. For some reason I don't recall if I made Gelasio into a VF. If I somehow didn't I'll do that as well. |
Observed behaviour
https://twitter.com/mjdye/status/1223762539768467456?s=19
Expected behaviour
Ligatures should be technically checked for existing, and visually checked for similarities. The latter might be more of an exq thing
The text was updated successfully, but these errors were encountered: