-
-
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
Apple CoreText two engines #50
Comments
@brawer |
Hello @brawer Could you please help create a test for this? |
I have no idea if/why CoreText would behave differently in different apps. If you can reproduce, consider filing a bug with Apple. If you tell me which specific CoreText APIs to call, I can change the test suite, or (preferred by me) just send a pull request via GitHub. |
This happens in notes app and browser while typing. when text is not in edit mode in browser, text is rendering correctly. Could we reproduce this issue in this test? here are text also |
Which CoreText API would need to be called exactly? (For the test suite, we need positioned glyph vectors which can be converted to outlines). The current code calls the regular CoreText and CoreGraphics APIs. If you know of another API that should be called, feel free to send a patch via GitHub. |
@brawer Hello Sascha,
There seems two modes or type of Text engine in MacOS and iOS.
First type has a lot of issues. How to test them separately?
Why is the difference?
I can give some sample text and show the difference, if it helps understanding this better.
The text was updated successfully, but these errors were encountered: