Skip to content
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

BREAKING CHANGE: CoreText now uses DirectWrite instead of FreeType #1336

Closed
ArnOmsft opened this issue Nov 8, 2016 · 0 comments
Closed

BREAKING CHANGE: CoreText now uses DirectWrite instead of FreeType #1336

ArnOmsft opened this issue Nov 8, 2016 · 0 comments

Comments

@ArnOmsft
Copy link
Member

ArnOmsft commented Nov 8, 2016

This month’s release includes a big change with CoreText now leveraging DirectWrite behind the scene instead of FreeType. This implementation offers several key advantages over the previous one:

  • Windows DirectWrite API supports measuring, drawing, and hit-testing of multi-format text
  • DirectWrite also provides a low-level glyph rendering API for developers who want to perform their own layout and Unicode-to-glyph processing
  • DirectWrite handles text in all supported languages for global and localized applications
  • Once we’ll have moved our CoreGraphics stack to Direct2D (more details about this coming change here), CoreText will be able to use hardware accelerated text rendering. For now, CoreText uses IWICBitmap to render text

Most of DirectWrite constructs to format and layout text map pretty well with CoreText. This lets us back most of the CoreText objects with DirectWrite object, allowing us to interact with DirectWrite in the backend without affecting the user facing CoreText APIs. You can find all the details about this change in the spec available here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant