search

unicode-org / text-rendering-tests

Unicode’s test suite for text rendering engines
Other
169 stars 37 forks source link

Apple CoreText two engines #50

Open MayuraVerma opened 6 years ago

MayuraVerma commented 6 years ago

@brawer Hello Sascha,

There seems two modes or type of Text engine in MacOS and iOS.

  1. Notes app, Twitter -new tweet window, youtube comment window
  2. Pages, emails, twitter- view tweet, youtube-comment view

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.

MayuraVerma commented 6 years ago

@brawer is it because of difference between NSTextView and NSTextField?

MayuraVerma commented 5 years ago

Hello @brawer

Could you please help create a test for this?

brawer commented 5 years ago

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.

MayuraVerma commented 5 years ago

This happens in notes app and browser while typing.

when text is not in edit mode in browser, text is rendering correctly. My guess, its something to do with nstextfield vs nstextview

Could we reproduce this issue in this test?

here are text ಅಕ್ಟ್ಬೋಬರ್ ಅಕ್ಟ್ರೋಬರ್‌ ಅರ್ಕ್ಟ್ರೋಬರ್ ಅರ್ಕ್ಟೋಬರ್

also ಕನ್ನಡೊ if it is at the beginning of the notes and no other text.

image1 image2

brawer commented 5 years ago

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.