-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Add DirectWrite into the test candidates? #47
Comments
This would be great! Pull requests welcome. (Sorry I can't do this myself; my last Windows machine was running NT 3.51). |
Also, I am not very sure whether DWrite could extract the path of "rendered" text. Maybe we need to implement bitmap comparison. |
cc. @fdwr |
@be5invis I'm also not on DWrite now :), but you totally can get the outline via IDWriteFontFace::GetGlyphRunOutline. If you want the outline for just a single glyph, pass a glyph count = 1. https://docs.microsoft.com/en-us/windows/desktop/api/dwrite/nf-dwrite-idwritefontface-getglyphrunoutline It calls back to your implementation of IDWriteGeometrySink with a series of AddLines and AddBeziers. https://docs.microsoft.com/en-us/windows/desktop/api/d2d1/nn-d2d1-id2d1simplifiedgeometrysink |
With Macintosh and AAT-specific cases removed.
The text was updated successfully, but these errors were encountered: