-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Instances created from some Noto VFs fail remove overlaps #3365
Comments
Not sure if this is something to do with the font or an issue with simplify itself |
@davelab6 perhaps instancing a few common locations would be a good bakery test for VFs? |
This occurs for Telugu as well:
Instances create fine at many other locations, something about the outlines at these positions seems to upset simplify. |
Agreed, good test fail cases. @moyogo could you take a look at the Fonts |
Sometimes skia-pathops simplify may fail (for unknown reasons which I'm still trying to debug). It's a good idea to know the name of the offending glyph google/fonts#3365
If I print the name of the glyph that fails with PathOpsError, I get 'cche.eth' and 'che.eth'. This is for NotoSansEthiopic[wdth,wght].ttf wdth=100 wght=800. I don't know why skia-pathops fails like that with those specific glyphs. I don't think there's anything wrong with the glyphs per se. I will try to reproduce using only skia and file an issue with upstream. |
If the Noto VFs are going to be corrected upstream, it would be nice to raise #3267 too: I haven't seen a single Noto VF with a correct |
@marekjez86 is fixing Noto STATs feasible? |
Anything unusual about them? Any pattern present in all the kerploding glyphs? |
I filed a bug upstream https://bugs.chromium.org/p/skia/issues/detail?id=11958 |
@anthrotype heads up, I'm observing the problem even after the rounding fix |
Our automation reported
|
Sometimes skia-pathops simplify may fail (for unknown reasons which I'm still trying to debug). It's a good idea to know the name of the offending glyph google/fonts#3365
The text was updated successfully, but these errors were encountered: